WordPress core is reviewed regularly by its security team, and serious issues are usually fixed quickly. Plugins are different: there are tens of thousands of them, written by developers of varying experience, and some go years without updates. Security vendors' reports consistently note that most disclosed WordPress vulnerabilities are in plugins. So the useful question is not "which plugin is dangerous" but "which type of flaw is dangerous, and how will I hear about it in time".
The most dangerous types
Unauthenticated file upload and remote code execution
The worst category. If a plugin fails to validate uploaded file types and lets anonymous visitors upload, an attacker can drop a PHP file and run any code. These flaws tend to appear in form, file manager, import and backup plugins, and automated scanners start probing sites very soon after disclosure.
Privilege escalation
A subscriber, or even an anonymous visitor, can turn themselves into an administrator, often because a profile or registration function does not restrict which fields can be changed. Unknown admins are the visible result.
Missing authorization in AJAX and REST
Actions via admin-ajax.php or the REST API must check capabilities and a nonce. Without that check, a simple request can change settings or export other users' data.
SQL injection, stored XSS and file read or delete
Unauthenticated SQL injection can leak password hashes and order data. Stored XSS runs in an administrator's browser. Arbitrary file read can expose the database password in wp-config.php, and arbitrary file deletion of that file sends WordPress to its install screen, letting an attacker connect the site to their own database.
| Type | Attacker gains | Typical sign |
|---|---|---|
| File upload / RCE | Full server control | PHP files in uploads |
| Privilege escalation | Admin account | Unknown admins |
| Missing authorization | Settings and data | Settings changed for no reason |
| SQL injection | Database contents | Odd queries in logs |
Which plugins carry more risk
Plugins handling files, users and payments: form and page builders, backup and migration tools, file managers, membership and LMS systems, shop add-ons. Abandoned plugins are a separate risk, since a flaw may never be fixed, and nulled premium plugins often ship with malware built in.
Tracking vulnerabilities
WPScan, Patchstack and Wordfence publish open databases listing affected and fixed versions. Use the CVSS score as a guide, but weigh it against your setup: an admin-only flaw is less urgent than an unauthenticated one.
wp plugin list --fields=name,status,version,update_version
wp plugin list --update=available
wp plugin update --all --dry-run
wpscan --url https://misol.uz --enumerate vp --api-token YOUR_TOKEN
Example: a hotel in Bukhara
A small hotel's site, misol.uz, used a booking plugin and had not been updated for a year. Days after an unauthenticated upload flaw was disclosed for the old version, unknown PHP files appeared in uploads and the site began sending spam. After cleanup the owner set a routine: review updates weekly, delete three unused plugins and enable auto-updates for minor security releases.
A practical routine
- Delete unused plugins with
wp plugin delete; inactive plugin files still sit on the server. - Enable
wp plugin auto-updates enable --allfor trusted plugins and test complex ones on a copy first. - Back up before every update, and buy premium plugins only from the vendor.
On sayt.uz hosting, ISPmanager backups make it quick to roll back a bad update. If a plugin flaw has already been exploited, updating alone is not enough: check for the signs above and remove malicious files and fake accounts as well.