dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-9172

HIGH · 7.5 CVSS v3.1 Published 2025-08-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
The Vibes plugin for WordPress is vulnerable to time-based SQL Injection via the ‘resource’ parameter in all versions up to, and including, 2.2.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 · high confidence

The Vibes WordPress plugin versions up to 2.2.0 contains an unauthenticated SQL injection vulnerability in the 'resource' parameter. The plugin fails to properly escape user-supplied input and does not use prepared statements, allowing attackers to inject malicious SQL queries. This time-based SQL injection can be used to extract sensitive data from the database.

MitigationUpdate the Vibes plugin to version 2.2.1 or later, which contains proper input sanitization and prepared SQL statements. If no patched version is available, disable the plugin until a fix 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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 Vibes plugin is installed
    Navigate to WordPress Admin > Plugins and locate the Vibes plugin in the list of installed plugins
    Affected if The Vibes plugin appears in the installed plugins list and is active
  2. Check installed Vibes plugin version
    In WordPress Admin > Plugins, click on the Vibes plugin details to view the installed version number
    Affected if The installed version is 2.2.0 or lower (versions 2.2.1 and later are patched)
  3. Confirm the plugin handles the 'resource' parameter
    Identify if the site uses the Vibes plugin functionality that processes the 'resource' parameter; this is typically accessed via HTTP requests to plugin endpoints
    Affected if The plugin is active and processes user input through the 'resource' parameter without authentication (unauthenticated endpoint)
  4. Compare version to affected range
    Compare your installed version against the affected range: any version up to and including 2.2.0 is vulnerable; version 2.2.1 and later are patched
    Affected if Your installed version is 2.2.0 or lower

You are affected if the Vibes WordPress plugin is installed at version 2.2.0 or lower and the plugin is active and accessible via the vulnerable 'resource' parameter endpoint.

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 Vibes plugin to version 2.2.1 or later, which contains proper input sanitization and prepared SQL statements. If no patched version is available, disable the plugin until a fix is released.

Recommended fix Moderate confidence

Version 2.2.1 or later

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the 'Vibes' plugin in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to the latest version (2.2.1 or higher)
  5. 5. Alternatively, download the latest version from the WordPress plugin repository
  6. 6. After updating, verify the plugin is active and functioning correctly
  7. 7. Consider running a security scan to confirm the vulnerability is no longer present

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

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-9172 — 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-9172 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