Safeguard
Vulnerability Analysis•

CVE-2021-24151: High Blind SQL Injection in WP Editor Plugin

CVE-2021-24151 is an authenticated blind SQL injection in the WP Editor WordPress plugin before 1.2.7. Update to 1.2.7 or later and review admin accounts.

Safeguard Security Team
3 min read

CVE-2021-24151 is a high severity (CVSS 7.2) blind SQL injection in the WP Editor plugin for WordPress, in versions before 1.2.7. It needs an administrator login and works through the settings save request. Update to WP Editor 1.2.7 or later.

What's affected

  • WP Editor (wp-editor) for WordPress, versions before 1.2.7, per the NVD record and WPScan.
  • Fixed in 1.2.7, per WPScan.
  • Severity conflict: NVD scores it 7.2 (High), while the WPScan entry lists CVSS 9.0 (critical). Both agree that an admin level login is needed.
  • The flaw needs an authenticated administrator or higher, so it matters most where admin accounts are shared or weakly protected.
  • KEV status: false.

How to check if you're exposed

Check the plugin version in the WordPress admin, or with WP-CLI.

wp plugin list --fields=name,status,version

If wp-editor is below 1.2.7, it is affected. Also review how many users hold the administrator role.

What to do now

  1. Update WP Editor to 1.2.7 or later, or remove it if you do not use it.
  2. Reduce administrator accounts to the people who need them and enable two factor authentication.
  3. Review database users: the WordPress database account should have only the privileges the site needs.
  4. Check logs for unusual requests to the settings save action.
  5. Keep plugins updated on a schedule, with a test step for important sites.

Why it matters

The class is CWE-89, SQL injection. The plugin did not sanitise or validate its settings fields, so an arbitrary parameter in the save request could alter a database query. Blind means the attacker does not see query output directly and infers data from how the site responds, which is slower but still workable.

It is tempting to ignore bugs that need admin access. The realistic risk is a stolen or reused admin password, or a lower privilege flaw elsewhere that leads to admin. Combining flaws is how many real incidents grow.

For WordPress sites in general, keep an inventory of installed plugins with their versions, delete the ones you do not use, and apply updates on a schedule. Most plugin flaws are fixed quickly by their authors, and the sites that get hurt are mostly the ones that never applied the fix. A weekly check with WP-CLI takes a few minutes and covers most of the risk.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Why do the scores differ?

NVD gives 7.2 and WPScan gives 9.0. They may weigh scope or impact differently. The fix is the same, so patch either way.

Does this need to be reachable by anyone on the internet?

No. The record says admin level authentication is needed.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.