Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site running Readabler < 2.0.18
-
DeliverySend crafted request with SQL payload
-
ExploitInjection executes in $wpdb query
-
ExecutionExtract database records
-
ImpactExfiltrate sensitive site 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 | The target must run the Readabler WordPress plugin at a version earlier than 2.0.18 with the plugin active and its vulnerable endpoint reachable over the network. Per the CVSS vector (PR:N/UI:N/AC:L), no authentication, no user interaction, and no special client-side conditions are required - exploitation works against default installations. The practical limiting factors are simply that the site must have this specific plugin installed and unpatched, and that the WordPress instance/endpoint is internet-reachable; there is no privilege, platform, or non-default-configuration barrier indicated in the data. |
| Impact | The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L) describes a high-severity, low-complexity, unauthenticated network attack with a confidentiality-focused impact and a scope change, which is consistent with SQL injection that can read data across the application boundary. However, the strong signals largely come from CVSS alone: there is no EPSS score, no KEV listing, and no POC in the provided data, so exploitation is theoretically easy but not confirmed to be occurring. The main mitigating factor for real-world prioritization is the product's moderate deployment footprint rather than any technical barrier - unauthenticated SQLi in default configurations should be treated as an urgent patch regardless of the missing EPSS/KEV signals. Note the impact metrics are somewhat unusual (I:N with A:L), suggesting a read-oriented injection rather than full data modification; verify actual write capability with the vendor advisory. |
| Exploit ScenarioDerived | An unauthenticated attacker sends a crafted HTTP request containing malicious SQL to a Readabler plugin endpoint on a target WordPress site running a version below 2.0.18. Because no authentication or user interaction is required, the attacker can automate scanning across many sites to extract sensitive database contents such as user records or password hashes. No public POC is identified at time of analysis, but the low attack complexity makes exploitation straightforward once the vulnerable endpoint is identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 18, 2026
SQL injection in the Readabler WordPress accessibility plugin (by Merkulove) before version 2.0.18 lets unauthenticated remote attackers inject arbitrary SQL against the site database. The CVSS 3.1 score is 9.3 with a scope change, reflecting that a low-privilege network request can reach and read backend data. No public exploit has been identified at time of analysis, and it is not in CISA KEV.
RemediationAI
Vendor-released patch: update the Readabler plugin to version 2.0.18 or later, which is the primary and definitive fix; consult the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/readabler/vulnerability/wordpress-readabler-plugin-2-0-18-sql-injection-vulnerability) for confirmation. If immediate upgrade is not possible, deploy a WAF rule (for example Patchstack's vPatch or an equivalent ruleset) to block SQL-injection patterns against the plugin's endpoints, and consider temporarily deactivating the Readabler plugin - the trade-off being loss of accessibility-toolbar functionality for site visitors until the update is applied. Restricting or monitoring database user privileges for the WordPress account can limit the blast radius but does not close the injection itself.
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
Readabler is a commercial accessibility toolbar plugin for WordPress developed by Merkulove (CPE cpe:2.3:a:merkulove:readabler). The flaw is CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), meaning user-controlled input reaches a database query without proper parameterization or sanitization. In WordPress plugins this class of bug typically arises when an AJAX/REST handler or front-end endpoint passes request parameters into a $wpdb query built by string concatenation, allowing an attacker to alter query logic and extract data from the WordPress database.
Know when Readabler 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
Unauthenticated network SQLi with low complexity (AV:N/AC:L/PR:N/UI:N); primary impact is data disclosure (C:H) with limited write potential (I:L), and I assess no scope change absent evidence the DB crosses a security authority (S:U).
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
Lifecycle Timeline
2DescriptionCVE.org
Unauthenticated SQL Injection in Readabler < 2.0.18 versions.
Executive ViewAI
The Readabler WordPress plugin contains a critical SQL injection vulnerability affecting all versions before 2.0.18 that allows unauthenticated attackers to directly query the website's database. This exposes customer data, user credentials, and sensitive business information stored in WordPress databases to unauthorized access and manipulation. Organizations running this accessibility plugin face immediate risk of data breach and should prioritize mitigation pending patch availability.
Disable or uninstall Readabler plugin pending patch availability. If plugin is essential for accessibility compliance, implement WAF rules targeting SQL injection payloads, restrict database user privileges to read-only where possible, enable comprehensive database query logging and alerting, and isolate WordPress instances on a restricted network segment. Monitor for indicators of compromise including unusual database query patterns and data access from unexpected sources.
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.
EUVD-2026-60819
GHSA-fv7m-82qw-8434
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB