Ally – Web Accessibility & Usability <= 4.0.3 - Unauthenticated SQL Injection via URL Path
Strategic Overview
- Status
- Patched in 4.1.0
- Affected Plugin
- Web Accessibility (formally known as Ally) – WCAG Scanning, Guided Fixes, Usability Widget
- Affected Version
<= 4.0.3- CVSS
- 7.5High
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2026-2413
At a glance
CVE-2026-2413 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Web Accessibility (formally known as Ally) WordPress plugin, affecting versions <= 4.0.3. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 4.1.0; sites on affected versions should update now. Disclosed March 2026, reported by Drew Webber (mcdruid).
Vulnerability Overview
The Ally – Web Accessibility & Usability plugin for WordPress is vulnerable to SQL Injection via the URL path in all versions up to, and including, 4.0.3. This is due to insufficient escaping on the user-supplied URL parameter in the `get_global_remediations()` method, where it is directly concatenated into an SQL JOIN clause without proper sanitization for SQL context. While `esc_url_raw()` is applied for URL safety, it does not prevent SQL metacharacters (single quotes, parentheses) from being injected. 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 via time-based blind SQL injection techniques. The Remediation module must be active, which requires the plugin to be connected to an Elementor account.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Web Accessibility (formally known as Ally) <= 4.0.3 carries this weakness at get_global_remediations(), and reaching it takes no account at all. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Web Accessibility (formally known as Ally) the fix is 4.1.0: builds <= 4.0.3 are affected, anything from 4.1.0 onward is not.
Remediation
Update to version 4.1.0, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Web Accessibility (formally known as Ally) 4.1.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Web Accessibility (formally known as Ally) – WCAG Scanning, Guided Fixes, Usability Widget
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C