dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-31579

CRITICAL · 9.3 CVSS v3.1 Published 2025-04-01
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 EXEIdeas International WP AutoKeyword wp-autokeyword allows SQL Injection.This issue affects WP AutoKeyword: from n/a through <= 1.0.

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

SQL injection vulnerability in the WP AutoKeyword WordPress plugin allows remote attackers to inject malicious SQL commands through unsanitized user input, potentially enabling unauthorized database access, data exfiltration, or complete application compromise.

MitigationUpdate to a patched version of the plugin immediately; if no patch is available, remove the plugin and implement parameterized queries or input sanitization as a temporary workaround.

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. Confirm WP AutoKeyword plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'WP AutoKeyword' in the list of active or inactive plugins.
    Affected if The plugin appears in the installed plugins list regardless of activation status, as the vulnerability may be exploitable even when the plugin is inactive if code remains on the server.
  2. Identify the installed plugin version
    In the Plugins list, click on 'WP AutoKeyword' to view the plugin details. Note the version number displayed. Alternatively, check the plugin folder via file manager or FTP at /wp-content/plugins/ for a version definition file.
    Affected if The installed version matches or falls within any vulnerable version ranges published in the official CVE disclosure.
  3. Determine if plugin public-facing features are enabled
    Review the plugin settings in WordPress admin under the plugin's configuration page. Check if any frontend-facing features such as keyword auto-linking, shortcodes, or public query parameters are enabled.
    Affected if The plugin exposes public endpoints or features that accept user input, as the SQL injection requires unsanitized user input to reach the vulnerable code path.
  4. Inspect HTTP access logs for suspicious SQL-like patterns
    Review web server access logs (Apache, Nginx, or WAF logs) for requests to your site containing SQL fragments such as 'UNION SELECT', 'OR 1=1', or other SQL keywords in query parameters that may target the plugin's AJAX endpoints or front-end forms.
    Affected if Log entries show SQL injection attempts targeting plugin-specific parameters or endpoints.
  5. Check database for signs of unauthorized access
    Review WordPress database tables, particularly wp_options and any custom tables created by the plugin, for unauthorized changes, new administrative users, or unexpected data modifications that may indicate prior exploitation.
    Affected if Unexpected modifications, unauthorized user accounts, or data anomalies are found that correlate with the time window since the plugin was installed.

The environment is affected if the WP AutoKeyword plugin is installed and its version falls within the vulnerable range disclosed for CVE-2025-31579, or if the plugin exposes any user input pathways that could be exploited for SQL injection.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of the plugin immediately; if no patch is available, remove the plugin and implement parameterized queries or input sanitization as a temporary workaround.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-31579 — 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-31579 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