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

> A local attacker can exploit a Cross-Site Scripting vulnerability in the VPN configuration module to obtain sensitive information.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Nov 2024
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-6gqj-7563-wqv6

## What is CVE-2024-28730?

CVE-2024-28730 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 Nov 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Cross Site Scripting vulnerability in DLink DWR 2000M 5G CPE With Wifi 6 Ax1800 and Dlink DWR 5G CPE DWR-2000M_1.34ME allows a local attacker to obtain sensitive information via the file upload feature of the VPN configuration module.

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

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

It affects 1 product.


Products: Dlink Dwr-2000m Firmware.

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

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

## Is CVE-2024-28730 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-28729](https://insights.sbomify.com/CVE-2024-28729/): Command injection in n/a (high 7.8)
- [CVE-2024-28731](https://insights.sbomify.com/CVE-2024-28731/): Cross-site request forgery in n/a (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-28730 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 Nov 2024. It can only be exploited from the same machine or local network, 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-28730 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-28730/ (Markdown: https://insights.sbomify.com/CVE-2024-28730/index.md)
```

## Sources

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

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