# CVE-2026-61875: luci-app-upnp Stored XSS via UPnP Port Mapping Description

> Unauthenticated LAN clients can inject JavaScript via UPnP port mapping descriptions, leading to stored XSS when administrators view the interface.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **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:** 12 Jul 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-xwgp-pprm-vcx3

## What is CVE-2026-61875?

CVE-2026-61875 is a high-severity cross-site scripting vulnerability in openwrt luci, published on 12 Jul 2026. 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

luci-app-upnp contains a stored cross-site scripting vulnerability that allows unauthenticated LAN clients to inject JavaScript via UPnP IGD AddPortMapping SOAP requests. Attackers can send malicious HTML in the NewPortMappingDescription field, which miniupnpd stores and luci-app-upnp renders without output encoding, executing the payload when administrators view the UPnP or Status pages.

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

## Which versions are affected by CVE-2026-61875?


## How do I fix CVE-2026-61875?

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

## Is CVE-2026-61875 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61875 and fix it if it is affected.

What it is: CVE-2026-61875 is a high-severity cross-site scripting vulnerability in openwrt luci, published on 12 Jul 2026. 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-2026-61875 exists.

Affected product: openwrt luci. 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-2026-61875/ (Markdown: https://insights.sbomify.com/CVE-2026-61875/index.md)
```

## Sources

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

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