Safeguard
Vulnerability Analysis•

CVE-2023-3211: Critical SQL Injection in WP Database Administrator

CVE-2023-3211 is a critical unauthenticated SQL injection in the WordPress Database Administrator plugin through 1.0.3. No fix is listed, so remove it.

Safeguard Security Team
3 min read

CVE-2023-3211 is a critical (CVSS 9.8) unauthenticated SQL injection in the WordPress Database Administrator plugin, versions through 1.0.3. WPScan lists no known fix. Until the vendor ships one, deactivate and remove the plugin, then review the database and access logs for signs of abuse.

What's affected

The NVD record covers the WordPress Database Administrator plugin through version 1.0.3. The vulnerable code path is an AJAX action that unauthenticated visitors can call, and one parameter is used in a SQL statement without proper sanitising or escaping.

Severity differs between sources. NVD scores this at 9.8 (critical) with a network, no privileges vector. The WPScan entry lists a CVSS of 8.6. Both put it in the high to critical range, and the unauthenticated access is the reason either way.

WPScan lists the plugin under the slug wp-database-admin and says there is no known fix at the time of the page we read. If the vendor has published a newer release since, treat that advisory as the source of truth.

How to check if you're exposed

If you manage WordPress with WP-CLI, list plugins and look for this one by name and version.

wp plugin list --format=table
wp plugin get wp-database-admin --fields=name,status,version

Without WP-CLI, open the Plugins page in the admin area and look for WordPress Database Administrator. Any version up to 1.0.3 is in scope.

Check web server logs for repeated requests to admin-ajax.php from addresses with no login, especially with unusual parameter values or long response times. That pattern can indicate probing of an injectable parameter.

What to do now

  1. Find every WordPress site you run or host that has the plugin installed, active or not.
  2. Deactivate and delete the plugin. A deactivated plugin may still leave files on disk, so delete rather than only switch it off.
  3. Replace the function with a maintained alternative, or use your host database tools instead of an in-dashboard database manager.
  4. Rotate database credentials and WordPress salts if you see signs of abuse in logs.
  5. Review recently created admin users and unexpected changes in the users and options tables.

Why it matters

The weakness is CWE-89, improper neutralization of special elements in an SQL command. The plugin passes user input into a query without separating data from code, and the endpoint does not require a login. That combination lets an outsider ask the database questions it should never answer.

A database administration plugin is a high value target by nature, since it already sits close to the data. The record does not state active exploitation and the CVE is not in the CISA KEV catalog, but unauthenticated SQL injection in a public plugin tends to get scanned for quickly.

Try it yourself

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

Quick check

Is it safe to keep the plugin if it is deactivated?

Deactivation stops the plugin code from loading, but the files remain on disk. Delete the plugin so no stray entry point stays reachable.

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.