CVE-2026-61875
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedluci-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA stored XSS vulnerability in luci-app-upnp allows unauthenticated LAN clients to inject malicious JavaScript via the NewPortMappingDescription field in UPnP IGD AddPortMapping SOAP requests. The payload is stored by miniupnpd and rendered without output encoding when administrators access UPnP or Status pages, enabling cookie theft or administrative action hijacking.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify luci-app-upnp is installedOn the OpenWrt device, run 'opkg list-installed | grep luci-app-upnp' or check /usr/lib/lua/luci/controller/upnp.lua existsAffected if The package is not installed or the lua controller file is missing (not affected)
-
Confirm miniupnpd service is enabled and runningRun '/etc/init.d/miniupnpd status' or check 'ps | grep miniupnpd' to see if the UPnP daemon is activeAffected if miniupnpd is not running (not affected - the persistence vector requires the daemon to store mappings)
-
Check UPnP port mappings for suspicious descriptionsRun 'upnpc -l' or inspect /var/miniupnpd.sqlite (or equivalent database) for port mappings - specifically examine the Description field of each mappingAffected if Any port mapping contains HTML/script tags in the description field (e.g., <script>, javascript:, onload=) indicating exploitation
-
Verify luci web interface is accessibleAttempt to access the luci web interface at the router's IP address on ports 80 or 443Affected if luci is accessible to attackers (required for the XSS to execute when admins view the UPnP status page)
-
Inspect luci UPnP view for unencoded outputView the UPnP status page in luci (System > Startup > UPnP or Status > UPnP) - check page source for raw HTML from description fieldsAffected if The description field content appears as raw HTML in the page without escaping (vulnerability is present)
User is affected if luci-app-upnp is installed, miniupnpd is enabled and accessible to LAN clients, and the luci web interface renders UPnP port mapping descriptions without HTML escaping.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply output encoding to the NewPortMappingDescription field before rendering in luci-app-upnp administrative pages; alternatively, disable UPnP if not required in the network environment.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-61875 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-61875 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data