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

> Remote attackers within Wi-Fi proximity can inject malicious scripts via SSID fields, potentially compromising user sessions on Hitron CODA-4582 routers.

- **Severity:** Medium 5.2 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Oct 2024
- **Updated:** 31 Oct 2024
- **Also known as:** GHSA-g56g-9mxr-9pgw

## What is CVE-2024-31973?

CVE-2024-31973 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Oct 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

Hitron CODA-4582 2AHKM-CODA4589 7.2.4.5.1b8 devices allow a remote attacker within Wi-Fi proximity to conduct stored XSS attacks via the 'Network Name (SSID)' input fields to the /index.html#wireless_basic page.

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

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


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

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

## Is CVE-2024-31973 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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