CVE-2018-0581
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 · uneditedCross-site scripting vulnerability in ASUS RT-AC87U Firmware version prior to 3.0.0.4.378.9383 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.
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 · moderate confidenceCross-site scripting vulnerability in ASUS RT-AC87U routers running firmware versions prior to 3.0.0.4.378.9383 allows remote attackers to inject arbitrary web script or HTML through unspecified vectors. The vulnerability is likely a stored XSS in the router's web management interface, where malicious scripts are persisted and executed when administrators access certain pages.
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< 3.0.0.4.378.9383CVSS 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.0/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.
-
Identify the router modelAccess the router's web management interface and check the device information page, or log into the router via SSH and run 'nvram get model' or check /proc/cpuinfoAffected if The device is not an ASUS RT-AC87U, then it is not affected by this specific CVE
-
Check the installed firmware versionLog into the router's web interface and navigate to the Administration > Firmware Upgrade page, or access the router via SSH and run 'nvram get firmver' and 'nvram get buildno'Affected if The firmware version is lower than 3.0.0.4.378.9383, the device is likely affected
-
Verify the web management interface is accessibleAttempt to access the router's web interface by entering the router's IP address in a web browserAffected if The web interface is accessible from the network, the stored XSS could be triggered when an administrator accesses the affected pages
-
Check for unauthorized remote administration settingsIn the web interface, navigate to Administration > System > Remote Management, or via SSH run 'nvram get http_wanport' to see if remote WAN access is enabled for the web interfaceAffected if Remote administration (WAN access) is enabled, the attack surface is wider and the vulnerability could be exploited remotely
If the device is an ASUS RT-AC87U running firmware versions prior to 3.0.0.4.378.9383 and has the web management interface accessible, it is likely affected by this stored XSS vulnerability.
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 data3.0.0.4.378.9383
Upgrade the ASUS RT-AC87U firmware to version 3.0.0.4.378.9383 or later. If upgrading is not possible, restrict administrative access to trusted networks only and monitor for suspicious activity.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0581 — 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-2018-0581 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