CVE-2025-2594 json
User Registration & Membership < 4.1.3 - Authentication Bypass
published last yr. modified 4mo ago also EUVD-2025-12286
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 9.5%
- EPSS 9.5% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB
Summary
The User Registration & Membership WordPress plugin before 4.1.3 does not properly validate data in an AJAX action when the Membership Addon is enabled, allowing attackers to authenticate as any user, including administrators, by simply using the target account's user ID.
Patch / fix
- Unknown User Registration & Membership 4.1.3
Is CVE-2025-2594 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-52302)
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
9.52% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-52302 WordPress User Registration & Membership Plugin 4.1.2 - Authentication Bypass webapps, 2025-05-25
- wpscan.com https://wpscan.com/vulnerability/1c1be47a-d5c0-4ac1-b9fd-475b382a7d8f/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Unknown User Registration & Membership
Classification
- Technology feeds
References
-
wpscan.com
/vulnerability/1c1be47a-d5c0-4ac1-b9fd-475b382a7d8f/
exploit, vdb-entry, technical-description, third-party-advisory
Sources
- CVE List CVE-2025-2594
- NVD CVE-2025-2594
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.