CVE-2025-4302VulnerabilityPublished 17 Jul 2025

CVE-2025-4302: Stop User Enumeration (WordPress plugin) · Observable Discrepancy

Affects Stop User Enumeration (WordPress plugin)Source CVE Database V5

Not known to be exploited · public detection template (Nuclei) · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.9% chance of exploitation in 30 days – higher than 62% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Jul 2025
Detectable: evidence found.
nuclei template: Stop User Enumeration WordPress plugin - Authentication Bypass
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Stop User Enumeration	Affected =0	Fixed in–

AI-suggested

European organizations should take immediate steps to mitigate this vulnerability. First, monitor for updates from the Stop User Enumeration plugin developers and apply version 1.7.3 or later as soon as it becomes available. Until a patch is released, organizations can implement web application firewall (WAF) rules to detect and block URL-encoded requests targeting the /wp-json/wp/v2/users/ endpoint. Custom rules should normalize URLs before inspection to prevent bypass via encoding. Additionally, restricting REST API access to authenticated users only, where feasible, can reduce exposure. Organizations should also audit their WordPress installations to identify if the vulnerable plugin is in use and assess the exposure of user enumeration endpoints. Employing rate limiting on REST API requests can further reduce the risk of automated enumeration attempts. Finally, educating administrators about this vulnerability and encouraging regular plugin updates and security best practices will help maintain a robust security posture.

Description

The Stop User Enumeration WordPress plugin before version 1.7.3 blocks REST API /wp-json/wp/v2/users/ requests for non-authorized users. However, this can be bypassed by URL-encoding the API path.

Impact

For European organizations using WordPress with the Stop User Enumeration plugin, this vulnerability poses a significant risk to user data confidentiality. Unauthorized user enumeration can expose usernames and potentially other user metadata, which can be exploited to facilitate targeted attacks such as credential stuffing, brute force login attempts, or spear phishing campaigns. Organizations in sectors with high regulatory requirements for data protection, such as finance, healthcare, and government, may face compliance risks if user information is exposed. Additionally, the reputational damage from a successful attack leveraging this vulnerability could be substantial. Since WordPress is widely used across Europe for websites ranging from small businesses to large enterprises, the scope of impact is broad. The vulnerability does not directly compromise system integrity or availability but serves as an enabler for more severe attacks. The lack of a patch at the time of disclosure increases the window of exposure, emphasizing the need for immediate mitigation. Given the ease of bypass via simple URL encoding, exploitation does not require advanced skills or authentication, increasing the likelihood of opportunistic attacks.

CWE-203Observable Discrepancy (opens in a new tab)
Base weakness
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
Implementation
Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended).
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Black Box Reverse Engineering (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

wpscan.com/vulnerability/19f67d6e-4ffe-4126-ac42-fb23c5017a3e (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Jul 2025, 08:01 UTC

Public exploits and detectiona Nuclei detection template

WeaknessesCWE-203

Technical details

References

Community reviews

Related threats