# CVE-2024-54248: WordPress Eewee Admin Custom plugin <= 1.8.2.4 - CSRF to Privilege Escalation vulnerability

> A CSRF vulnerability in the Eewee Admin Custom WordPress plugin allows attackers to escalate privileges by tricking users into performing actions.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Dec 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-c429-2q48-3x6w

## What is CVE-2024-54248?

CVE-2024-54248 is a high-severity vulnerability in eewee admin custom, published on 13 Dec 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-Site Request Forgery (CSRF) vulnerability in eewee eewee admin custom eewee-admincustom allows Privilege Escalation.This issue affects eewee admin custom: from n/a through <= 1.8.2.4.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2024-54248 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-54248 is a high-severity vulnerability in eewee admin custom, published on 13 Dec 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-54248 in the wild and no public exploit code.

Affected product: eewee admin custom. 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-54248/ (Markdown: https://insights.sbomify.com/CVE-2024-54248/index.md)
```

## Sources

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

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