# CVE-2026-107424: WordPress Frontend Dashboard plugin <= 3.0.7 - Privilege Escalation vulnerability

> Attackers can escalate privileges due to incorrect privilege assignment in the Frontend Dashboard WordPress plugin.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-grrc-h2jw-4w99

## What is CVE-2026-107424?

CVE-2026-107424 is a critical vulnerability in M A Vinoth Kumar Frontend Dashboard, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incorrect Privilege Assignment vulnerability in M A Vinoth Kumar Frontend Dashboard frontend-dashboard allows Privilege Escalation.This issue affects Frontend Dashboard: from n/a through 3.0.7.

Weakness: CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2026-107424?


## How do I fix CVE-2026-107424?

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

## Is CVE-2026-107424 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107424 and fix it if it is affected.

What it is: CVE-2026-107424 is a critical vulnerability in M A Vinoth Kumar Frontend Dashboard, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-107424 in the wild and no public exploit code.

Affected product: M A Vinoth Kumar 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-2026-107424/ (Markdown: https://insights.sbomify.com/CVE-2026-107424/index.md)
```

## Sources

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

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