dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-23931

CRITICAL · 9.3 CVSS v3.1 Published 2025-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Oliver Fuhrmann WordPress Local SEO dh-local-seo allows Blind SQL Injection.This issue affects WordPress Local SEO: from n/a through <= 2.3.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A blind SQL injection vulnerability exists in the dh-local-seo WordPress plugin (versions <= 2.3) due to improper neutralization of special elements in SQL commands. Attackers can exploit this by injecting malicious SQL queries through unsanitized user input, potentially allowing extraction of sensitive data from the database or complete database compromise.

MitigationUpdate the dh-local-seo plugin to the latest patched version if available. If no patch exists, disable the plugin immediately and implement a WAF rule as a temporary compensating control until a secure version is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify dh-local-seo plugin is installed
    In WordPress admin, navigate to Plugins > Installed Plugins and look for 'dh-local-seo' in the list, or check the /wp-content/plugins/ directory for the dh-local-seo folder
    Affected if The plugin folder dh-local-seo exists in /wp-content/plugins/ and the plugin is activated
  2. Check the installed plugin version
    In WordPress admin, click on the dh-local-seo plugin to view its details and locate the version number, or open the main plugin file (usually dh-local-seo.php) and look for the 'Version' header in the plugin comments
    Affected if The version number is 2.3 or lower, or if no version is displayed and the plugin has not been updated since early 2025
  3. Identify user input entry points
    Review the plugin files in /wp-content/plugins/dh-local-seo/ for PHP files containing $_GET, $_POST, or $_REQUEST superglobals that pass user input to database queries, particularly in AJAX handlers or form processing files
    Affected if The plugin contains files that accept user input and directly incorporate it into SQL queries without using $wpdb->prepare() or similar parameterized query methods
  4. Check for suspicious database activity
    Review WordPress debug logs (wp-content/debug.log if enabled) and server access logs for unusual SQL syntax or error messages originating from dh-local-seo plugin files, or check for unexpected outbound connections from the server
    Affected if SQL errors, unusual query patterns, or evidence of SQL injection attempts targeting dh-local-seo endpoints appear in logs
  5. Audit database user permissions
    Check the WordPress database user credentials in wp-config.php and verify they have only the minimum required privileges; examine the database for any unexpected new tables or modified existing tables that may indicate exploitation
    Affected if The WordPress database user has overly broad permissions (such as DROP, ALTER, or FILE privileges) or unauthorized tables/data exist in the WordPress database

If dh-local-seo plugin versions 2.3 or lower are installed and active, and the plugin processes user-supplied input without proper SQL sanitization, the environment is vulnerable to CVE-2025-23931

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the dh-local-seo plugin to the latest patched version if available. If no patch exists, disable the plugin immediately and implement a WAF rule as a temporary compensating control until a secure version is released.

Recommended fix Moderate confidence

Latest available version of WordPress Local SEO plugin (dh-local-seo) after version 2.3

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Local SEO' plugin (dh-local-seo) by Oliver Fuhrmann
  4. Check the current installed version (should be <= 2.3)
  5. Navigate to Plugins > Add New
  6. Search for 'Local SEO' by Oliver Fuhrmann
  7. Install and activate the latest available version of the plugin
  8. Verify the new version is > 2.3 and the plugin functions correctly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-23931 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-23931 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data