# CVE-2024-49593: Cross-site scripting in n/a

> Stored XSS in Advanced Custom Fields allows attackers to execute scripts via the Field Group editor, impacting WordPress sites using the plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2024
- **Updated:** 18 Nov 2024
- **Also known as:** GHSA-q285-mcqv-8j69

## What is CVE-2024-49593?

CVE-2024-49593 is a medium-severity cross-site scripting vulnerability in n/a, published on 17 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Advanced Custom Fields (ACF) before 6.3.9 and Secure Custom Fields before 6.3.6.3 (plugins for WordPress), using the Field Group editor to edit one of the plugin's fields can result in execution of a stored XSS payload. NOTE: if you wish to use the WP Engine alternative update mechanism for the free version of ACF, then you can follow the process shown at the advancedcustomfields.com blog URL within the References section below.

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

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


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

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

## Is CVE-2024-49593 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-49593 is a medium-severity cross-site scripting vulnerability in n/a, published on 17 Oct 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-49593 in the wild and no public exploit code.

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

## Sources

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

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