# CVE-2024-53278: Cross-site scripting in WP Admin UI Customize

> A malicious admin can inject scripts into the WordPress admin interface, allowing arbitrary code execution in other users' browsers.

- **Severity:** Medium 4.8 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Nov 2024
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-ghx6-2rmh-c36g

## What is CVE-2024-53278?

CVE-2024-53278 is a medium-severity cross-site scripting vulnerability in gqevu6bsiz WP Admin UI Customize, published on 26 Nov 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting vulnerability exists in WP Admin UI Customize versions prior to ver 1.5.14. If a malicious admin user customizes the admin screen with some malicious contents, an arbitrary script may be executed on the web browser of the other users who are accessing the admin screen.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2024-53278 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-53278 is a medium-severity cross-site scripting vulnerability in gqevu6bsiz WP Admin UI Customize, published on 26 Nov 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-53278 in the wild and no public exploit code.

Affected product: gqevu6bsiz WP Admin UI Customize. 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-53278/ (Markdown: https://insights.sbomify.com/CVE-2024-53278/index.md)
```

## Sources

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

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