Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach vulnerable WP Data Access endpoint
-
DeliverySubmit crafted SQL injection payload
-
ExploitTrigger blind SQL query execution
-
ExecutionInfer and extract database records
-
ImpactExfiltrate credentials and sensitive data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires a deployment of the WP Data Access WordPress plugin at version 5.5.82 or earlier with a reachable vulnerable parameter/endpoint. Per the supplied CVSS vector (AV:N/AC:L/PR:N/UI:N), no user interaction is needed and the vector indicates remote unauthenticated reachability against the affected plugin; however, this unauthenticated claim is not corroborated by the description and should be confirmed against the Patchstack advisory, since comparable plugin SQLi often requires at least subscriber-level authentication. The primary limiting factor is that the site must have this specific plugin installed and unpatched; the blind nature of the injection increases the number of requests needed for data extraction but does not prevent exploitation. |
| Impact | This is a genuine high-priority issue by severity signals but with important caveats. The CVSS 3.1 base score is 9.3 (Critical) driven by a network, low-complexity, no-privilege, no-user-interaction vector with a scope change (S:C) and high confidentiality impact - consistent with blind SQL injection exposing the full WordPress database (user credentials, hashes, secrets). However, several exploitation signals are MISSING from the input: no EPSS probability, no CISA KEV listing, and no POC indicator, so real-world exploitation likelihood cannot be quantified - status is 'no public exploit identified at time of analysis.' Note a tension in the provided vector: it reports PR:N (unauthenticated), yet many Patchstack-reported WordPress plugin SQLi flaws in practice require at least low-privilege (subscriber/author) authentication - this should be verified against the Patchstack advisory, because if authentication is actually required the real-world risk is materially lower than the 9.3 implies. The impact profile (C:H, I:N, A:L) matches data exfiltration rather than data tampering or full takeover. Bottom line: treat as high priority for patching given the critical CVSS and the sensitivity of WordPress databases, but recognize that absent EPSS/KEV/POC evidence this is a 'high-CVSS, unproven-exploitation' case rather than confirmed active threat. |
| Exploit ScenarioDerived | An attacker sends crafted input to a vulnerable WP Data Access plugin endpoint that is interpolated into a SQL query without proper neutralization. Using blind (inference-based) techniques such as boolean or time-based payloads, the attacker iteratively extracts database contents - including WordPress user accounts and password hashes - enabling follow-on account compromise. The CVSS AV:N/AC:L vector indicates this is remotely reachable with low effort, though no public exploit code is confirmed in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
Blind SQL injection in the WordPress WP Data Access plugin through version 5.5.82 could allow a remote attacker to read sensitive database contents; the supplied CVSS vector rates it 9.3 with PR:N, indicating network-reachable unauthenticated exploitation, though the provided advisory data does not independently corroborate the unauthenticated condition and comparable plugin SQLi often requires at least subscriber-level access. This is a genuine high-priority issue by severity signals but with important caveats, and no public exploit identified at time of analysis.
RemediationAI
No fixed version is listed in the provided data, so the vendor-released patch status is not independently confirmed; monitor the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/wp-data-access/vulnerability/wordpress-wp-data-access-plugin-5-5-82-sql-injection-vulnerability?_s_id=cve and upgrade WP Data Access beyond 5.5.82 as soon as the vendor publishes a patched release. If the plugin is not essential, deactivate and remove it, which eliminates the vulnerable SQL injection surface at the cost of losing its database management functionality. If it must remain, apply a virtual patch or WAF rule that blocks SQL injection patterns and rate-limits requests to plugin endpoints to slow blind extraction, accepting possible false positives and incomplete coverage because blind SQLi can evade generic signatures; also restrict administrative access to the plugin, monitor logs for anomalous repeated requests, and confirm whether the vulnerable endpoint truly allows unauthenticated access or requires at least subscriber-level authentication, since that affects the necessary compensating controls.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
WP Data Access is a WordPress plugin that provides database management and data access features, and the CPE cpe:2.3:a:passionate_programmer_peter:wp_data_access:*:*:*:*:*:*:*:* identifies the affected product. The root cause class is CWE-89, improper neutralization of special elements used in an SQL command, and the specific issue is blind SQL injection, meaning an attacker typically cannot see query output directly and must infer data through boolean- or time-based responses, which can require many requests but still enables data extraction. The CVSS vector AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L indicates network reachability, low attack complexity, no required privileges or user interaction per the vector, a scope change, high confidentiality impact, no integrity impact, and low availability impact; the independent assessment notes that the PR:N unauthenticated claim comes from the vector and is not corroborated by the description, so deployment-specific authentication requirements should be confirmed against the Patchstack advisory.
Know when Wp Data Access gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
Blind SQLi exposing a separate database component justifies S:C and C:H; AV:N/AC:L/PR:N follow the supplied vector, though PR:N is uncertain and may warrant PR:L if authentication is actually required.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Passionate Programmer Peter WP Data Access allows Blind SQL Injection.
This issue affects WP Data Access: from n/a through 5.5.82.
Articles & Coverage 1
Executive ViewAI
The WP Data Access WordPress plugin through version 5.5.82 contains a critical blind SQL injection vulnerability (CVE-2026-95605) that could expose sensitive database contents on affected sites. Because the supplied CVSS vector indicates unauthenticated network exploitation (PR:N) and the severity is 9.3, any organization hosting this plugin should treat exposed WordPress instances as high risk, especially those storing customer, employee, or proprietary data. Leadership should prioritize immediate inventory and mitigation because no vendor-released patch identified at time of analysis and no public exploit identified at time of analysis.
No vendor-released patch identified at time of analysis. Interim mitigations include disabling or removing the WP Data Access plugin where possible; if it must remain, restrict access to trusted authenticated users, deploy WAF rules to detect and block SQL injection attempts, enforce least privilege on the WordPress database account, monitor database and web logs for anomalous queries, and isolate affected WordPress instances from sensitive data stores.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
More in Wp Data Access
View allThe WP Data Access WordPress plugin before 5.0.0 does not properly sanitise and escape the backup_date parameter before
SQL injection in the WP Data Access WordPress plugin (versions <= 5.5.81) lets remote unauthenticated attackers inject a
Unauthorized export of complete database table contents in the WP Data Access WordPress plugin before 5.5.84 lets unauth
Unauthenticated attackers can modify data in the WP Data Access WordPress plugin before version 5.5.77 by abusing one of
Unauthenticated SQL injection in the WP Data Access WordPress plugin (versions <= 5.5.70) allows remote attackers to inj
The WP Data Access plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 5.3.7. R
Unauthenticated SQL injection in the WordPress plugin WP Data Access affects all versions up to and including 5.5.84, al
Unauthenticated reflected cross-site scripting in WP Data Access WordPress plugin (versions up to and including 5.5.79)
Stored Cross-Site Scripting in WP Data Access WordPress plugin versions up to and including 5.5.79 is exploitable by use
Broken access control in WP Data Access WordPress plugin versions 5.5.80 and earlier exposes protected data to unauthent
Cross-Site Request Forgery (CSRF) vulnerability in Passionate Programmers B.V. Rated medium severity (CVSS 4.3), this vu
EUVD-2026-94490
GHSA-89mw-3f7g-8gfx
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB