Frontend Dashboard 1.0 - 2.2.7 - Missing Authorization to Authenticated (Subscriber+) Privilege Escalation via fed_admin_setting_form_function Function
Strategic Overview
- Status
- Patched in 2.2.8
- Affected Plugin
- Frontend Dashboard
- Affected Version
1.0 – 2.2.7- CVSS
- 8.8High
- Weakness type
- CWE-285 · Improper Authorization
- CVE
CVE-2025-4474
At a glance
CVE-2025-4474 is a high-severity Improper Authorization vulnerability in the Frontend Dashboard WordPress plugin, affecting versions 1.0 – 2.2.7. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.2.8; 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_admin_setting_form_function() function in versions 1.0 to 2.2.7. This makes it possible for authenticated attackers, with Subscriber-level access and above, to overwrite the plugin’s 'register' role setting to make new user registrations default to the administrator role, leading to an elevation of 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 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.7 carries this weakness at register, and reaching it takes an account at Subscriber level or above. 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.8: builds 1.0 – 2.2.7 are affected, anything from 2.2.8 onward is not.
Remediation
Update to version 2.2.8, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Frontend Dashboard 2.2.8 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