Frontend Dashboard 1.0 - 2.2.6 - Missing Authorization to Unauthenticated Privilege Escalation via fed_wp_ajax_fed_login_form_post Function
Strategic Overview
- Status
- Patched in 2.2.7
- Affected Plugin
- Frontend Dashboard
- Affected Version
1.0 – 2.2.6- CVSS
- 9.8Critical
- Weakness type
- CWE-285 · Improper Authorization
- CVE
CVE-2025-4104
At a glance
CVE-2025-4104 is a critical-severity Improper Authorization vulnerability in the Frontend Dashboard WordPress plugin, affecting versions 1.0 – 2.2.6. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.2.7; sites on affected versions should update now. Disclosed May 2025, reported by kr0d.
Vulnerability Overview
The Frontend Dashboard plugin for WordPress is vulnerable to Privilege Escalation due to a missing capability check on the fed_wp_ajax_fed_login_form_post() function in versions 1.0 to 2.2.6. This makes it possible for unauthenticated attackers to reset the administrator’s email and password, and elevate their privileges to that of an administrator.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-285: Improper Authorization
Frontend Dashboard 1.0 – 2.2.6 carries this weakness at fed_wp_ajax_fed_login_form_post(), and reaching it takes no account at all. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.
A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For Frontend Dashboard the fix is 2.2.7: builds 1.0 – 2.2.6 are affected, anything from 2.2.7 onward is not.
Remediation
Update to version 2.2.7, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Frontend Dashboard 2.2.7 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Frontend Dashboard
- 8.8CVE-2024-8268: Frontend Dashboard <= 2.2.4 Arbitrary Function Call
CVE-2024-8268 - 7.5CVE-2025-46248: Frontend Dashboard <= 2.2.5 SQL Injection
CVE-2025-46248 - 6.4CVE-2025-49310: Frontend Dashboard <= 2.2.8 Stored XSS
CVE-2025-49310 - 6.4CVE-2024-29775: Frontend Dashboard <= 2.2.1 Stored XSS
CVE-2024-29775 - 5.3CVE-2024-32726: Frontend Dashboard <= 2.2.2 Info Exposure
CVE-2024-32726
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C