Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach WordPress directory filter endpoint
-
DeliverySubmit crafted w2dc_level_filter parameter
-
ExploitInject SLEEP-based SQL conditional
-
ExecutionInfer data via response timing
-
ImpactExfiltrate sensitive database contents
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 | Exploitation targets the directory-listing filter feature via the specific 'w2dc_level_filter' request parameter, which is placed into a SQL query in integer context without surrounding quotes; this specific placement is why WordPress's built-in addslashes/magic_quotes escaping provides no protection against SLEEP-based time-based payloads. It affects all versions up to and including 2.10.12 and no non-default configuration is described as required. The principal limiting factors are: (1) the privilege level is unresolved - the description says unauthenticated but the CVSS vector encodes PR:L, so authentication may in fact be required; and (2) the blind/time-based technique yields data slowly through timing inference rather than direct output, making bulk extraction slow and detectable. |
| Impact | This is a moderate-priority issue with a notable internal data conflict that must be resolved before final triage. The supplied CVSS:3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, base 6.5) encodes PR:L, implying an authenticated attacker, yet the description explicitly states 'unauthenticated attackers' can exploit it - these two signals disagree, and the true privilege requirement should be verified with Wordfence/the vendor before prioritization. If the description is correct (unauthenticated), real-world risk is meaningfully higher than the 6.5 score suggests and an independent recompute lands near 7.5. The flaw is a time-based (blind) SQL injection via an integer-context parameter, which the description confirms defeats WordPress's addslashes/magic_quotes escaping - a credible, well-understood exploitation primitive. Countervailing factors: no EPSS score was provided, the CVE is NOT in CISA KEV, no public exploit or PoC code is indicated in the references (only a Wordfence threat-intel page and the CodeCanyon product listing), and the blind/time-based nature makes extraction slow and noisy rather than instantaneous. The vuln.today decision label is 'this_month' - meaningful but not emergency/act_now. Net: a legitimate issue warranting patching on a normal cycle, elevated if the unauthenticated claim holds, but not currently evidenced as under active or automated exploitation. |
| Exploit ScenarioDerived | An attacker sends a crafted request to the directory-listing filter functionality with a malicious 'w2dc_level_filter' value containing a SLEEP-based conditional; by observing response delays the attacker infers database contents one boolean at a time and gradually extracts sensitive data such as user records or credentials hashes. The description indicates no authentication is needed, though the supplied CVSS vector's PR:L contradicts this. No public exploit code is identified in the provided references. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 31, 2026
Time-based blind SQL injection in the Web 2.0 Directory plugin for WordPress (all versions up to and including 2.10.12) lets an attacker inject SLEEP-style conditional payloads through the 'w2dc_level_filter' parameter of the directory-listing filter and infer database contents from response timing. Because the parameter is interpolated into the query in integer context without surrounding quotes, WordPress's built-in addslashes/magic_quotes escaping does not neutralise the payload. The primary open question is privilege: the reporter describes the flaw as reachable by unauthenticated attackers, while the supplied CVSS vector encodes PR:L and our assessment records PR:N, so authentication requirements are not definitively resolved from the available data; extraction is also slow and detectable because it relies on blind timing inference. No public exploit code has been identified at time of analysis, and the issue is prioritised as this_month rather than as an emergency.
RemediationAI
No vendor-released patch is identified in the available data: neither advisory reference publishes a fixed version, so the first action is to check the CodeCanyon item page (https://codecanyon.net/item/web-20-directory-plugin-for-wordpress/6463373) and the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/317e155b-5d7b-447b-93db-65b5f242a66d?source=cve) for a release later than 2.10.12 and apply it as soon as it is published. Until such a build is confirmed, the most complete mitigation is to deactivate and remove the plugin, accepting the loss of directory functionality as the trade-off. If the directory must stay live, restrict or block requests carrying the 'w2dc_level_filter' parameter at the reverse proxy or WAF, understanding that legitimate level-filtering links will break, and constrain the WordPress database account to the minimum privileges the site actually needs so that injected subqueries cannot reach other schemas or file primitives. Because the injection is time-based, watch database and web-server logs for anomalous response latency and repeated filter requests from the same source as a detection and triage signal; this is a compensating control only and not a substitute for a fixed plugin version.
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
The fault class is CWE-89, SQL injection, in a commercial WordPress plugin distributed through CodeCanyon (shamalli:web_2.0_directory_plugin_for_wordpress). The vulnerable path is the directory-listing filter feature, where the request parameter 'w2dc_level_filter' is concatenated into an existing SQL statement rather than bound as a prepared-statement placeholder. The distinguishing detail is context: the value lands in an integer comparison without surrounding quotes, so the escaping WordPress applies to superglobals (addslashes-style, historically magic_quotes-derived) never reaches the point where it would matter, and time-based conditional payloads such as SLEEP() execute as intended. Impact is confidentiality-only per both the supplied and assessed vectors (C:H, I:N, A:N, S:U), meaning the attacker reads data through timing side channels rather than modifying or destroying it. The two competing severity pictures reflect the unresolved privilege question: the reporter's narrative implies an unauthenticated visitor to a directory page can trigger the query, while the declared vector's PR:L would require a low-privileged account; our independent assessment adopts PR:N with AV:N/AC:L/UI:N, giving 7.5 rather than the supplied 6.5. Practically, timing-oracle injection yields data slowly and generates measurable latency in server responses, which raises the chance of detection but does not reduce the sensitivity of what can ultimately be read.
Know when Web 2 0 Directory Plugin For Wordpress 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:L/UI:N/S:U/C:H/I:N/A:N
Description states unauthenticated network exploitation (AV:N/AC:L/PR:N/UI:N); blind SQLi reads data (C:H) but does not modify or disrupt (I:N/A:N); PR:N chosen over the input's PR:L per the explicit 'unauthenticated' claim.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
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.
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-114713
GHSA-gxv8-xvj3-3gm9
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB