# CVE-2025-0354: Cross-site scripting in WG2600HM4

> An attacker can inject arbitrary scripts into NEC Aterm routers via the network, potentially leading to code execution or account takeover.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jan 2025
- **Updated:** 3 Apr 2025
- **Also known as:** GHSA-qgh2-59hq-68f3

## What is CVE-2025-0354?

CVE-2025-0354 is a medium-severity cross-site scripting vulnerability in NEC Corporation WG2600HM4, published on 15 Jan 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting vulnerability in NEC Corporation Aterm WG2600HS Ver.1.7.2 and earlier, WG2600HP4 Ver.1.4.2 and earlier, WG2600HM4 Ver.1.4.2 and earlier, WG2600HS2 Ver.1.3.2 and earlier, WX3000HP Ver.2.4.2 and earlier and WX4200D5 Ver.1.2.4 and earlier allows a attacker to inject an arbitrary script via the network.

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

## Which versions are affected by CVE-2025-0354?


## How do I fix CVE-2025-0354?

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

## Is CVE-2025-0354 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0354 and fix it if it is affected.

What it is: CVE-2025-0354 is a medium-severity cross-site scripting vulnerability in NEC Corporation WG2600HM4, published on 15 Jan 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-0354 in the wild and no public exploit code.

Affected product: NEC Corporation WG2600HM4. 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-2025-0354/ (Markdown: https://insights.sbomify.com/CVE-2025-0354/index.md)
```

## Sources

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

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