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

> A disputed XSS vulnerability in jQuery UI allows remote attackers to execute arbitrary code and read sensitive data via crafted payloads.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L`)
- **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:** 17 Oct 2024
- **Updated:** 25 Oct 2024
- **Also known as:** GHSA-g4r7-cj36-63v3

## What is CVE-2024-30875?

CVE-2024-30875 is a high-severity cross-site scripting vulnerability in n/a, published on 17 Oct 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 Scripting vulnerability in JavaScript Library jquery-ui v.1.13.1 allows a remote attacker to obtain sensitive information and execute arbitrary code via a crafted payload to the window.addEventListener component. NOTE: this is disputed by the Supplier because it cannot be reproduced, and because the exploitation example does not indicate whether, or how, the example website is using jQuery UI.

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

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


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

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

## Is CVE-2024-30875 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-30875 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-30875 is a high-severity cross-site scripting vulnerability in n/a, published on 17 Oct 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-30875 exists.

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-30875/ (Markdown: https://insights.sbomify.com/CVE-2024-30875/index.md)
```

## Sources

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

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