Web 2.0 Directory <= 2.10.12 - Unauthenticated SQL Injection via 'w2dc_level_filter' Parameter
Strategic Overview
- Status
- Patched in 3.0.0
- Affected Plugin
- Web 2.0 Directory plugin for WordPress
- Affected Version
<= 2.10.12- CVSS
- 6.5Medium
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command
- CVE
CVE-2026-15272
At a glance
CVE-2026-15272 is a medium-severity Improper Neutralization of Special Elements used in an SQL Command vulnerability in the Web 2.0 Directory plugin for WordPress WordPress plugin, affecting versions <= 2.10.12. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 3.0.0; sites on affected versions should update now. Disclosed October 2026, reported by Rafie Muhammad.
Vulnerability Overview
The Web 2.0 Directory plugin for WordPress is vulnerable to time-based SQL Injection via the 'w2dc_level_filter' parameter in all versions up to, and including, 2.10.12 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. 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. Because the parameter is used in integer context without surrounding quotes, WordPress's built-in addslashes/magic_quotes escaping provides no protection against time-based payloads such as SLEEP-based conditionals.
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 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
Web 2.0 Directory plugin for WordPress <= 2.10.12 carries this weakness at w2dc_level_filter, 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 2.0 Directory plugin for WordPress the fix is 3.0.0: builds <= 2.10.12 are affected, anything from 3.0.0 onward is not.
Remediation
Update to version 3.0.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 2.0 Directory plugin for WordPress 3.0.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C