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

> Remote attackers within Wi-Fi proximity can inject malicious scripts into router configuration fields, potentially compromising user sessions.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/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:** 19 Mar 2024
- **Updated:** 31 Oct 2024
- **Also known as:** GHSA-hpmw-vh9j-2pxc

## What is CVE-2024-28092?

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

### Official description

UBEE DDW365 XCNDDW365 8.14.3105 software on hardware 3.13.1 allows a remote attacker within Wi-Fi proximity to conduct stored XSS attacks via RgFirewallEL.asp, RgDdns.asp, RgTime.asp, RgDiagnostics.asp, or RgParentalBasic.asp. The affected fields are SMTP Server Name, SMTP Username, Host Name, Time Server 1, Time Server 2, Time Server 3, Target, Add Keyword, Add Domain, and Add Allowed Domain.

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

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


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

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

## Is CVE-2024-28092 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-28092 is a high-severity cross-site scripting vulnerability in n/a, published on 19 Mar 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-28092 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-28092/ (Markdown: https://insights.sbomify.com/CVE-2024-28092/index.md)
```

## Sources

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

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