Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in WPVibes WP Mail Log allows DOM-Based XSS. This issue affects WP Mail Log: from n/a through 1.0.2.
Product
wordpress stop-user-enumeration vulnerabilities
7 published CVES affecting wordpress stop-user-enumeration, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 7
- Critical
- 0
- High
- 3
- Medium
- 4
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest wordpress stop-user-enumeration CVEs
Newest publication first
-
HighCVSS 7.1 EPSS 0.27%
-
MediumCVSS 5.3 EPSS 0.98%
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.
-
MediumCVSS 6.1 EPSS 2.0%
The stop-user-enumeration plugin before 1.3.8 for WordPress has XSS.
-
HighCVSS 8.8
The Freemius SDK for WordPress is vulnerable to authorization bypass due to a missing capability check on the _get_db_option and _set_db_option functions in versions up to, and including, 2.2.3. This makes it possible for authenticated attackers, with subscriber-level permissions...
-
MediumCVSS 5.3 EPSS 2.1%
Stop User Enumeration 1.3.8 allows user enumeration via the REST API
-
MediumCVSS 5.3
The Stop User Enumeration plugin for WordPress is vulnerable to Username Enumeration Bypasses in versions up to, and including, 1.3.4. This makes it possible for unauthenticated attackers to enumerate lists of valid users that can be used for future attacks.
-
WORDFENCE-f8a653ab-7703-4e73-8089-a15ba6cf9718 Stop User Enumeration <= 1.2.4 - Security Bypass
PublishedHighCVSS 7.3The WordPress Stop User Enumeration Plugin for WordPress is vulnerable to Security Bypass in versions up to, and including, 1.2.4 via POST requests as the protection only functions as intended with GET requests. This makes it possible for unauthenticated attackers to perform othe...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.