CVE-2021-32019
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 · uneditedThere is missing input validation of host names displayed in OpenWrt before 19.07.8. The Connection Status page of the luci web-interface allows XSS, which can be used to gain full control over the affected system via ICMP.
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 confidenceOpenWrt versions before 19.07.8 contain a stored XSS vulnerability in the luci web interface's Connection Status page. The page displays host names without proper input validation or output sanitization, allowing attackers to inject malicious JavaScript. This XSS can be leveraged to execute commands with privileges sufficient to control the system via ICMP.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 19.07.0, < 19.07.8CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Check OpenWrt version via command lineRun 'cat /etc/openwrt_release' or 'cat /etc/os-release' to view the installed OpenWrt versionAffected if The version displayed is less than 19.07.8 (for example, 19.07.0 through 19.07.7)
-
Check OpenWrt version via LuCI web interfaceLog into the LuCI web interface and navigate to System > System or Status > Overview to view the OpenWrt versionAffected if The version shown is before 19.07.8
-
Verify LuCI is installed and enabledCheck if the luci package is installed by running 'opkg list-installed | grep luci' or check if the web interface is accessible on port 80 or 443Affected if LuCI is installed and the web interface is accessible (required for the XSS to be exploitable)
-
Confirm the Connection Status page is accessibleAccess the LuCI web interface and navigate to Network > Diagnostics or Status > Connection Status page where host names are displayedAffected if The Connection Status page is reachable and displays host name information (this is the vulnerable component)
You are affected if your OpenWrt version is 19.07.0 through 19.07.7 AND the LuCI web interface is installed and accessible, as the stored XSS exists in the Connection Status page's host name display functionality.
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 data19.07.8
Upgrade OpenWrt to version 19.07.8 or later which includes proper input validation for host names displayed in the luci interface. Until upgraded, restrict access to the luci web interface to trusted users only.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-32019 — 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-2021-32019 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