Privilege escalation via forged default-role update
Published Apr 8, 2025 · Updated Apr 8, 2026
CSRF in WPFront User Role Editor for WordPress 4.2.1 and earlier allows remote attackers to alter the default role via a forged request. The whitelist_options() function processes the role-setting update without correctly validating a nonce, causing an administrator's session to change the multisite default. Exploitation requires a multisite instance and an authenticated site administrator to visit attacker-controlled content; the changed default enables privilege escalation.
Summary
What happened
CSRF in WPFront User Role Editor for WordPress 4.2.1 and earlier allows remote attackers to alter the default role via a forged request. The whitelist_options() function processes the role-setting update without correctly validating a nonce, causing an administrator's session to change the multisite default. Exploitation requires a multisite instance and an authenticated site administrator to visit attacker-controlled content; the changed default enables privilege escalation.
The record
- CVE
- CVE-2025-3064
- Published
- Apr 8, 2025
- Updated
- Apr 8, 2026
- Vendor
- Syam Mohan
- Product
- WPFront User Role Editor
- Classifications
- CWE-352, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 8, 2025CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=4.2.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo