dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-42665

CRITICAL · 9.3 CVSS v3.1 Published 2026-06-15
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
Unauthenticated SQL Injection in WP Data Access <= 5.5.70 versions.

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

Unauthenticated SQL injection in WP Data Access WordPress plugin versions 5.5.70 and below allows remote attackers to execute arbitrary SQL commands without authentication via unspecified input vectors.

MitigationUpdate WP Data Access plugin to the latest version immediately. If no patched version is available, consider disabling 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
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. Locate WP Data Access plugin version
    Check the main plugin file (usually wp-content/plugins/wp-data-access/wp-data-access.php or similar) for the 'Version' header, or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'wp_data_access_version' OR option_name LIKE '%wp_data_access%version%';
    Affected if The plugin is installed and the version cannot be determined or is 5.5.70 or lower
  2. Compare installed version to affected range
    If version was found, compare it numerically to 5.5.70. Any version 5.5.70 or lower (including 5.5.69, 5.5.68, etc.) is within the affected range.
    Affected if The installed version is 5.5.70 or any version lower than 5.5.70
  3. Verify plugin is active
    Query WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' AND option_value LIKE '%wp-data-access%'; or check via WordPress admin under Plugins > Installed Plugins.
    Affected if The plugin appears in active plugins and is currently enabled on the site
  4. Check for SQL injection indicators
    Review web server error logs and WordPress debug logs for SQL syntax errors, especially those containing UNION, SELECT, or database table names that appear to originate from wp-data-access endpoints. Also check access logs for unusual query patterns to plugin AJAX handlers or public-facing endpoints.
    Affected if SQL errors or suspicious database queries are found in logs referencing WP Data Access functionality

The environment is affected if WP Data Access plugin is installed, active, and the installed version is 5.5.70 or lower, since the unauthenticated SQL injection vulnerability is present in all such versions.

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 WP Data Access plugin to the latest version immediately. If no patched version is available, consider disabling the plugin until a fix is released.

Recommended fix Moderate confidence

Upgrade to the latest available version of WP Data Access (greater than 5.5.70)

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Locate WP Data Access in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  6. 6. Verify the update was successful by checking the plugin version (should be greater than 5.5.70)
  7. 7. Test critical functionality to ensure the plugin still works correctly after the update
Caveat Minor or major compatibility issues possible if using older PHP/WordPress versions or conflicting plugins - test in staging first

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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