# CVE-2024-56071: WordPress Simple Dashboard plugin <= 2.0 - Privilege Escalation vulnerability

> Attackers can escalate privileges due to incorrect privilege assignment in the Simple 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:** 31 Dec 2024
- **Updated:** 11 May 2026
- **Also known as:** GHSA-vxm9-cgrp-h5gq

## What is CVE-2024-56071?

CVE-2024-56071 is a critical vulnerability in mikeleembruggen Simple Dashboard, published on 31 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incorrect Privilege Assignment vulnerability in mikeleembruggen Simple Dashboard simple-dashboard allows Privilege Escalation.This issue affects Simple Dashboard: from n/a through <= 2.0.

Weakness: CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2024-56071?


## How do I fix CVE-2024-56071?

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

## Is CVE-2024-56071 being exploited?

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

Public exploit code:

- Simple Dashboard <= 2.0 - Unauthenticated Privilege Escalation (github_poc): https://github.com/Nxploited/CVE-2024-56071

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-56071 and fix it if it is affected.

What it is: CVE-2024-56071 is a critical vulnerability in mikeleembruggen Simple Dashboard, published on 31 Dec 2024. 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-2024-56071 in the wild and no public exploit code.

Affected product: mikeleembruggen Simple 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-2024-56071/ (Markdown: https://insights.sbomify.com/CVE-2024-56071/index.md)
```

## Sources

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

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