# CVE-2025-4474: Missing authorization in Frontend Dashboard

> Authenticated subscribers can escalate privileges to administrator by exploiting a missing capability check in the Frontend Dashboard plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 May 2025
- **Updated:** 13 May 2025
- **Also known as:** GHSA-fvjp-r2gf-q2qc

## What is CVE-2025-4474?

CVE-2025-4474 is a high-severity missing authorization vulnerability in vinoth06 Frontend Dashboard, published on 13 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2025-4474?


## How do I fix CVE-2025-4474?

No fix has been published for CVE-2025-4474 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-4474 being exploited?

There is no known exploitation of CVE-2025-4474 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-4474 and fix it if it is affected.

What it is: CVE-2025-4474 is a high-severity missing authorization vulnerability in vinoth06 Frontend Dashboard, published on 13 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-4474 in the wild and no public exploit code.

Affected product: vinoth06 Frontend Dashboard. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-4474/ (Markdown: https://insights.sbomify.com/CVE-2025-4474/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-4474
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-4474
- OSV: https://osv.dev/vulnerability/CVE-2025-4474

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-4474/
Summaries are generated and may contain mistakes; the official description above is the record.