Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WordPress site with User Frontend plugin
-
DeliveryLocate exposed user directory search endpoint via POC guidance
-
ExploitSend unauthenticated HTTP request with broad search query
-
ExecutionReceive full user PII list including admins
-
ImpactHarvest emails and phone numbers for phishing or credential stuffing
Vulnerability Assessment
| Weakness |
CWE
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No special conditions are required beyond the User Frontend plugin being installed and active on a WordPress site running a version in the 4.3.0-4.3.9 range - the vulnerable endpoint is exposed by default with no non-default configuration needed. The CVSS vector AV:N/AC:L/PR:N/UI:N confirms remote unauthenticated exploitation against default plugin configurations. What limits exploitation: the attacker must be able to reach the WordPress site over the network, and the specific endpoint path must be known or discovered (trivial via the public POC); the impact is limited to confidentiality of PII (email and phone) and does not extend to authentication bypass, remote code execution, or integrity modification. |
| Impact | The CVSS 3.1 base score of 5.3 (Medium) reflects a network-accessible, unauthenticated, low-complexity attack with no user interaction required, but only partial confidentiality impact and no integrity or availability impact - a characterization that is consistent with a mass PII enumeration flaw. SSVC signals reinforce the automatable:yes designation, meaning a single script can enumerate the entire user database without manual intervention; however, SSVC exploitation is rated 'none' at time of analysis and CISA KEV confirms no active exploitation. EPSS data was not provided, limiting probabilistic exploitation forecasting. The most consequential signal here is the publicly available POC combined with the automatable nature: while the CVSS score is medium, the ease of bulk PII exfiltration - including admin email addresses usable in targeted phishing or credential stuffing - elevates practical risk above what the raw score implies. The vendor CPE lists the vendor as 'unknown,' which limits independent verification of deployment scope. |
| Exploit ScenarioDerived | An attacker identifies a WordPress site running the vulnerable User Frontend plugin, then sends automated unauthenticated HTTP GET or POST requests to the exposed user directory search endpoint with wildcard or empty query parameters. The endpoint returns structured data containing email addresses and phone numbers for all registered users including administrators, which the attacker harvests for targeted phishing campaigns or credential stuffing attacks. A publicly available POC reduces the skill threshold for exploitation to near zero. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 28, 2026
Unauthenticated mass PII enumeration in the User Frontend WordPress plugin (versions 4.3.0 through 4.3.10) exposes the email address and phone number of every registered user - including site administrators - via an unrestricted user directory search endpoint. The flaw requires no authentication, no special configuration, and is automatable per SSVC, making bulk harvesting trivial for any remote attacker. A publicly available proof-of-concept exploit exists, reported by WPScan, though active exploitation has not been confirmed by CISA KEV at time of analysis.
RemediationAI
Upgrade the User Frontend WordPress plugin to version 4.3.10 or later, which contains the vendor-released patch. The fix is available via the WordPress plugin repository or the vendor advisory referenced at https://wpscan.com/vulnerability/1ff904bd-cb9e-4530-afb4-6842395bb774/. If an immediate upgrade is not feasible, a targeted compensating control is to block unauthenticated HTTP requests to the plugin's user directory search endpoint via WAF rules or server-level access controls (e.g., nginx location blocks or Apache mod_rewrite rules restricting the specific endpoint path to authenticated sessions only). As a trade-off, this may break legitimate front-end directory search functionality for logged-out visitors. Disabling the plugin entirely is the most complete workaround if the directory feature is non-essential.
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 vulnerability stems from CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor): the plugin exposes a user directory search REST or AJAX endpoint without enforcing WordPress authentication or capability checks. Under the affected CPE (cpe:2.3:a:unknown:user_frontend:*:*:*:*:*:*:*:*), versions in the 4.3.x branch prior to 4.3.10 are impacted. WordPress plugins commonly register custom endpoints via wp_ajax_nopriv_ or REST API routes without permission_callback, and failing to restrict these routes is the root cause class here. The plugin likely surfaces this endpoint as part of a front-end user directory or member search feature, exposing structured PII in the response body.
Know when User Frontend 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:U/C:L/I:N/A:N
Network-exposed unauthenticated endpoint with no complexity; confidentiality limited to PII fields only, no integrity or availability impact.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
3DescriptionCVE.org
The User Frontend WordPress plugin before 4.3.10 does not restrict access to its user directory search endpoint, allowing unauthenticated attackers to retrieve the email address and phone number of every registered user, including administrators.
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in User Frontend
View allPHP Object Injection in the User Frontend WordPress plugin (versions before 4.3.11) allows any authenticated subscriber-
PHP object injection via unsafe deserialization in the User Frontend WordPress plugin (versions before 4.3.10) grants Ed
Unauthenticated attachment deletion in the User Frontend WordPress plugin before 4.3.8 allows remote attackers to perman
Unauthenticated post creation and publication is possible in the User Frontend WordPress plugin before 4.3.11 due to a s
PHP object injection in User Frontend plugin for WordPress versions up to 4.3.1 allows authenticated attackers with Subs
Authorization bypass in the WP User Frontend (WPUF) WordPress plugin through version 4.3.7 allows unauthenticated visito
Unauthenticated content tampering in the WP User Frontend WordPress plugin (all versions through 4.3.7) allows any visit
Unauthenticated attackers can modify arbitrary WordPress posts through the User Frontend plugin (versions up to 4.2.8) d
Insecure Direct Object Reference in weDevs WP User Frontend plugin (all versions ≤4.3.1) allows unauthenticated network
Unauthorized subscription cancellation in weDevs User Frontend WordPress plugin (all versions through 4.3.2) allows any
EUVD-2026-67568
GHSA-vwp5-qxw4-4vgw
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB