CVE-2026-62948: OpenWrt odhcpd/LuCI: unauthenticated DHCPv6 client can inject lease-file lines via FQDN hostname → stored XSS in the LuCI admin UI
OpenWrt is a Linux operating system targeting embedded devices. Prior to 25.12.5, odhcpd writes a DHCPv6 client FQDN option 39 hostname into /tmp/odhcpd.leases through src/statefiles.c statefiles_write_state6() and statefiles_write_state4() without escaping, allowing newline injection of forged lease lines that LuCI rpcd-mod-luci getDHCPLeases displays through htdocs/luci-static/resources/view/status/include/40_dhcp.js and htdocs/luci-static/resources/luci.js dom.append as live HTML in the Active DHCPv6 Leases admin page. This vulnerability is fixed in 25.12.5.
Security readout for executives and security teams
Plain-English summary
A malicious device on a network could plant data that OpenWrt later shows inside the LuCI admin interface as active content. An administrator viewing DHCPv6 leases could trigger the stored XSS. The issue is rated critical and fixed in OpenWrt 25.12.5.
Executive priority
Treat this as urgent for OpenWrt infrastructure with LuCI enabled or untrusted local network clients. The required admin interaction lowers immediacy compared with fully automatic compromise, but successful XSS can affect confidentiality, integrity, and availability.
Technical view
Before 25.12.5, odhcpd wrote DHCPv6 FQDN option 39 hostnames into lease state files without escaping. Newline injection could create forged lease entries, which LuCI rendered as live HTML in the Active DHCPv6 Leases page, producing stored XSS.
Likely exposure
OpenWrt routers and embedded devices running versions before 25.12.5 are potentially affected. Highest concern is on systems where untrusted DHCPv6 clients can interact with odhcpd and administrators use the LuCI web interface.
Exploitation context
The source bundle marks KEV as false and provides no evidence of active exploitation. The documented path requires unauthenticated DHCPv6 client input plus administrator interaction with the LuCI DHCPv6 leases view.
Researcher notes
The evidence points to a chained data-handling issue: insufficient output escaping in odhcpd lease serialization and unsafe LuCI rendering. The bundle cites fixes in both odhcpd and LuCI, but does not provide exploit-in-the-wild evidence.
Mitigation direction
Upgrade OpenWrt to 25.12.5 or later.
Prioritize devices exposed to untrusted or guest DHCPv6 clients.
Restrict LuCI access to trusted management networks.
Review OpenWrt advisory and release notes for device-specific guidance.
Avoid viewing DHCPv6 leases on unpatched systems unless necessary.
Validation and detection
Inventory OpenWrt devices and confirm installed version.
Identify systems running OpenWrt earlier than 25.12.5.
Confirm whether LuCI is installed and used for administration.
Review DHCPv6 exposure to guest, user, or untrusted networks.
Verify remediation by confirming OpenWrt 25.12.5 or later.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-117: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.