dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-9010

HIGH · 7.5 CVSS v3.1 Published 2026-05-20
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 Boost plugin for WordPress is vulnerable to time-based SQL Injection via the 'current_url' and 'user_name' parameters in versions up to, and including, 2.0.3 due to insufficient escaping on the user supplied parameters and lack of sufficient preparation on the existing SQL queries. 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 · moderate confidence

The WordPress Boost plugin versions up to 2.0.3 contains a time-based SQL injection vulnerability in the 'current_url' and 'user_name' parameters. Unauthenticated attackers can append malicious SQL queries due to insufficient input sanitization and lack of prepared statements in existing database queries, potentially allowing extraction of sensitive data from the database.

MitigationUpdate to the latest patched version of the Boost plugin when available. Until then, implement WAF rules to block SQL injection attempts on the affected parameters and consider disabling the plugin if exposure is critical.

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. Confirm Boost plugin is installed
    Navigate to WordPress admin > Plugins, or check the wp-content/plugins directory for a folder named 'boost' or similar. Also check wp-content/plugins/ for jetboost or similar naming patterns.
    Affected if Boost plugin is found in the WordPress installation
  2. Identify the installed Boost plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate Boost. The version number is displayed below the plugin name. Alternatively, open the main plugin PHP file (usually boost.php or jetboost.php) and look for 'Version:' in the plugin header comment.
    Affected if Version is 2.0.3 or lower (versions up to and including 2.0.3 are vulnerable)
  3. Verify the plugin exposes vulnerable parameters
    The vulnerability affects 'current_url' and 'user_name' parameters. These are used by the plugin for URL tracking and user attribution. Check if the plugin's frontend features are active and accessible without authentication (the vulnerability is unauthenticated).
    Affected if Plugin is active and these features are in use without authentication restrictions
  4. Check for signs of SQL injection exploitation
    Review web server access logs (Apache/nginx) for suspicious patterns in URL parameters named 'current_url' or 'user_name', especially with SQL keywords (UNION, SELECT, SLEEP, etc.) or unusual time delays. Also check WordPress debug logs if enabled.
    Affected if Log entries show SQL injection attempts in these parameters, or database contains unexpected entries

You are affected if the Boost plugin is installed with version 2.0.3 or lower and the vulnerable current_url/user_name parameters are accessible to unauthenticated users.

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 to the latest patched version of the Boost plugin when available. Until then, implement WAF rules to block SQL injection attempts on the affected parameters and consider disabling the plugin if exposure is critical.

Recommended fix Moderate confidence

Latest version newer than 2.0.3 (confirm fix is included in release notes)

  1. Check the official WordPress plugin repository or the plugin developer's website for the latest version of the Boost plugin
  2. Verify if a version newer than 2.0.3 is available and confirm it includes the SQL injection fix
  3. Update the plugin to the latest version through the WordPress admin dashboard or via FTP
  4. After updating, verify the fix by checking plugin changelog or release notes for security fixes related to SQL injection
Caveat Review plugin changelog for any breaking changes before upgrading

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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