dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-67950

HIGH · 8.5 CVSS v3.1 Published 2025-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable 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 Syed Balkhi All In One SEO Pack all-in-one-seo-pack allows Blind SQL Injection.This issue affects All In One SEO Pack: from n/a through <= 4.9.1.

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 All In One SEO Pack WordPress plugin (versions up to 4.9.1). The vulnerability allows attackers to inject malicious SQL commands through unsanitized user input that flows into database queries, potentially enabling unauthorized data extraction or manipulation.

MitigationUpgrade to the latest version of All In One SEO Pack (4.9.2 or later) which contains the patched code. If immediate upgrade is not possible, disable the plugin until patched.

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/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. Check if All In One SEO Pack plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'All In One SEO Pack' in the list of active plugins.
    Affected if The plugin appears in the list of installed plugins (whether active or inactive).
  2. Identify the installed version number
    In the Plugins page, click on 'All In One SEO Pack' to view plugin details, or hover over the plugin row to see the version number displayed.
    Affected if The displayed version is 4.9.1 or earlier.
  3. Verify the version via WordPress plugin files
    If admin access is limited, access the server filesystem and check the main plugin file (aioseop-class.php or similar) in the /wp-content/plugins/all-in-one-seo-pack/ directory for the 'Version' header in the plugin comment block.
    Affected if The version header in the plugin file reads 4.9.1 or lower.
  4. Confirm plugin status and exposure
    Review whether the plugin is active and accessible via the WordPress site. SQL injection requires the vulnerable code to be reachable, so note if the plugin is deactivated.
    Affected if The plugin is active and the site is accessible to unauthenticated or low-privilege users who could trigger the vulnerable input points.

A WordPress site is affected if All In One SEO Pack version 4.9.1 or earlier is installed and the plugin is active, since the vulnerable code handles unsanitized user input in database queries.

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

Upgrade to the latest version of All In One SEO Pack (4.9.2 or later) which contains the patched code. If immediate upgrade is not possible, disable the plugin until patched.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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