🛡️
Security

Securing a DLE Site: Licensing, the Admin Panel and the uploads Folder

19.11.2026
← All articles

DataLife Engine (DLE) is a commercial content management system widely used by news portals, regional information sites and online magazines across the former Soviet region. It is fast, its template system is simple, and it suits newsrooms that publish a lot. Yet the security of a DLE site usually depends less on the software itself than on how it was installed and maintained.

Nulled copies: the most expensive saving

Because DLE is paid software, "free" copies with the licence check removed circulate widely. Whoever distributes such a copy can add any code they like, and in practice they often do: a hidden admin login, a script that takes commands from a remote server, or injected advertising links. Picture a regional news site in Andijan that publishes dozens of stories a day and ranks well, until a search engine finds casino spam on its pages and starts showing a warning. The cause is often foreign code that has lived inside the system since day one. Get DLE only from the official site with a licence, which also gives you access to security updates.

Updates and add-on modules

Many DLE sites stay on old versions for years because heavily customised templates might break. Instead of avoiding updates, clone the site to a test domain such as test.misol.uz, update there first, then apply it to production. Modules from forums deserve the same caution: inspect them for eval, base64_decode or calls to external hosts, and remove unused modules entirely.

Lock down the admin panel

The panel lives at admin.php by default, and bots try passwords there all day. DLE lets you rename the panel file and set the new name in system settings; check the official documentation for your version. Restricting access to newsroom IP addresses is even more effective:

<Files "admin.php">
    Require ip 203.0.113.10 198.51.100.0/24
</Files>

If staff work from changing mobile connections, add HTTP authentication to the panel file instead. Use long unique passwords and delete accounts of people who have left.

No PHP execution in uploads

Web shells on DLE sites are most often hidden in uploads, disguised as images or archives. Only media and documents belong there, so make sure PHP cannot run:

# uploads/.htaccess
<FilesMatch "\.(php|phtml|phar|php[0-9]|pl|py|cgi)$">
    Require all denied
</FilesMatch>
Options -ExecCGI -Indexes

If Nginx serves the site directly, .htaccess is ignored and the rule belongs in the server configuration.

File permissions and secrets

Old guides suggest 777 everywhere, but on modern hosting the site runs as its own user and 755 for directories and 644 for files is normally enough. Tighten the files holding database credentials:

find . -type d -exec chmod 755 {} \;
find . -type f -exec chmod 644 {} \;
chmod 640 engine/data/dbconfig.php engine/data/config.php

Afterwards confirm that the site, the panel, image uploads and the cache still work.

Hunting for foreign code

find uploads/ -type f -name "*.php"
find . -type f -name "*.php" -mtime -10
grep -rlE "eval\(|base64_decode\(|gzinflate\(" --include="*.php" engine/ templates/

Not every match is malicious, since some legitimate modules use these functions, but any PHP file inside uploads almost certainly is. After cleaning, change every password, including the database password, or the attacker may simply return.

Backups and monitoring

For a news site the worst damage is losing years of archive. Back up the database and uploads regularly and keep copies off the server. The sayt.uz hosting panel offers backup and restore, but keeping your own extra copy of a valuable archive is wise. Review error and access logs from time to time: floods of requests to admin.php or hits on unknown PHP files are warning signs.

Related articles

🖱️ Clickjacking: protecting your site with X-Frame-Options and CSP 🔐 Adding Passkeys to Your Website: A Practical WebAuthn Guide 🧩 Outdated plugins: the most common reason websites get hacked 🚪 Does Changing the SSH Port Help? Myth vs Reality
🌐 Language
🇺🇿 O'zbek 🇺🇿 Ўзбек 🇷🇺 Русский 🇬🇧 English ✓