CVE-2018-0582
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-AC68U Firmware version prior to 3.0.0.4.380.1031 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 confidenceStored cross-site scripting (XSS) vulnerability in ASUS RT-AC68U router firmware allows remote attackers to inject arbitrary JavaScript/HTML into the web management interface via unspecified input vectors. The vulnerability exists prior to firmware version 3.0.0.4.380.1031 and could enable session hijacking, credential theft, or admin action execution through the compromised router interface.
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.380.1031CVSS 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.
-
Confirm device model is ASUS RT-AC68ULog into the router web interface or check the device label/packaging to verify the exact model numberAffected if The device is not an ASUS RT-AC68U model, then it is not affected by this specific CVE
-
Check installed firmware versionAccess the router web management interface, navigate to Administration > Firmware Upgrade or similar section, and note the displayed firmware version numberAffected if The installed firmware version is lower than 3.0.0.4.380.1031 (for example, 3.0.0.4.380.912 or earlier)
-
Verify web management interface is enabledCheck router settings under Administration > System > Enable Web GUI from WAN or similar option to see if the remote management interface is accessible from external networksAffected if The web management interface is exposed to the internet or untrusted networks, increasing the attack surface for this XSS vulnerability
-
Inspect router configuration for anomaliesReview the router's web interface settings, particularly input fields in sections like Network Setup, Wireless, or Port Forwarding, for unexpected JavaScript code or HTML tags that may indicate past exploitationAffected if Suspicious scripts or HTML markup are found in router configuration fields that were not intentionally added
You are affected if you have an ASUS RT-AC68U router running firmware version 3.0.0.4.380.1031 or earlier, especially if the web management interface is accessible from external networks.
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.380.1031
Upgrade ASUS RT-AC68U firmware to version 3.0.0.4.380.1031 or later. If upgrading is not immediately possible, restrict administrative interface access to trusted networks and monitor for suspicious admin panel activity.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0582 — 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-0582 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