CVE-2025-3605 json
Frontend Login and Registration Blocks <= 1.1.1 - Unauthenticated Privilege Escalation via Account Takeover
published 2025-05-09 18 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-14130
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.7%
- EPSS 7.7% chance of exploitation in 30 days, percentile 94%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
The Frontend Login and Registration Blocks plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 1.1.1. This is due to the plugin not properly validating a user's identity prior to updating their details like email via the flr_blocks_user_settings_handle_ajax_callback() function. This makes it possible for unauthenticated attackers to change arbitrary user's email addresses, including administrators, and leverage that to reset the user's password and gain access to their account.
Timeline
- Published
- First public exploit (EDB-52291)
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 18 mo ago
Exploit prediction
7.70% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-52291 WordPress Frontend Login and Registration Blocks Plugin 1.0.7 - Privilege Escalation webapps, 2025-05-13
- Nuclei template WordPress Frontend Login and Registration Blocks Plugin 1.0.7 - Privilege Escalation nuclei detection template
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- arkenon Login, Registration and Lost Password Blocks
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
- Technology feeds
References
Sources
- CVE List CVE-2025-3605
- NVD CVE-2025-3605
Fencer Vulns 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.