Wireless Lan Controller SoftwareOperating system · Cisco
CVE-2015-0726
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 · uneditedThe web administration interface on Cisco Wireless LAN Controller (WLC) devices before 7.0.241, 7.1.x through 7.4.x before 7.4.122, and 7.5.x and 7.6.x before 7.6.120 allows remote authenticated users to cause a denial of service (device crash) via unspecified parameters, aka Bug IDs CSCum65159 and CSCum65252.
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 confidenceDenial of service vulnerability in Cisco Wireless LAN Controller web administration interface. Authenticated remote users can send specially crafted parameters to the web UI causing the device to crash. Requires valid credentials but no other complexity is described.
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
Wireless Lan Controller SoftwareOperating system
= 7.0.98.0= 7.0.98.218= 7.0.116.0= 7.0.220.0= 7.0_base= 7.4.1.54= 7.4.100= 7.4.100.60= 7.4.110.0= 7.4.121.0= 7.4_base= 7.6.100.0CVSS 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
- Authentication
- Single
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:S/C:N/I:N/A:C
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 installed WLC software versionLog into the Cisco WLC CLI and run the command 'show inventory' or 'show version' to retrieve the installed software version.Affected if The displayed version matches one of the affected versions: 7.0.98.0, 7.0.98.218, 7.0.116.0, 7.0.220.0, 7.0_base, 7.4.1.54, 7.4.100, 7.4.100.60, 7.4.110.0, 7.4.121.0, 7.4_base, or 7.6.100.0
-
Verify web administration interface is enabledRun the command 'show web-auth' or check the WLC web interface configuration to confirm the web-based management interface is active.Affected if The web administration interface is enabled and accessible over HTTP/HTTPS
-
Confirm management access methodCheck if the WLC is configured to allow web-based management using 'show run-config' or by reviewing the management interface settings.Affected if The device allows remote web-based management access
The device is affected if it runs an affected Cisco WLC software version listed above and has the web administration interface enabled, as the vulnerability is triggered through specially crafted parameters sent to the web UI.
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 dataUpgrade Cisco WLC firmware to version 7.0.241, 7.4.122, or 7.6.120 or later per the version matrix. Apply during a planned maintenance window as the device will reboot during upgrade.
Fix this in Wireless Lan Controller Software
Scoped from the published advisory
- Consultation3.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 $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0726 — 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-2015-0726 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