CVE-2021-26967
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 · uneditedA remote reflected cross-site scripting (xss) vulnerability was discovered in Aruba AirWave Management Platform version(s): Prior to 8.2.12.0. A vulnerability in the web-based management interface of AirWave could allow a remote attacker to conduct a reflected cross-site scripting (XSS) attack against a user of certain components of the interface. A successful exploit could allow an attacker to execute arbitrary script code in a victim’s browser in the context of the AirWave management interface.
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 confidenceA remote reflected XSS vulnerability exists in Aruba AirWave Management Platform web interface. An attacker can craft malicious URLs containing script code that gets executed in victim's browser when they access certain components of the management interface, allowing session hijacking or actions in the context of the authenticated user.
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< 8.2.12.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
- 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.
-
Verify AirWave is installedCheck if Aruba AirWave Management Platform is deployed in your environment by reviewing your inventory, running processes, or consulting with system administrators who manage network management tools.Affected if AirWave is not present in your environment, this CVE does not apply.
-
Identify the installed AirWave versionAccess the AirWave web login page and look for the version number typically displayed on the login screen, or log in and navigate to the About/Dashboard section. Alternatively, access the CLI and run commands such as 'show version' or check version files in the installation directory.Affected if Unable to determine the version indicates AirWave may be present but version information is not accessible through standard methods.
-
Compare version against affected rangeTake the identified version and compare it to the affected range: any version lower than 8.2.12.0 is vulnerable. For example, 8.2.11.0, 8.2.10.0, 8.2.9.0, 8.2.8.0, and earlier major versions like 8.2.x, 8.0.x, and 7.x are all affected.Affected if Your installed version is less than 8.2.12.0, meaning you are running a vulnerable version.
-
Assess web interface exposureDetermine if the AirWave web management interface is accessible from network locations where untrusted users could craft malicious URLs. Check firewall rules, VPN requirements, and whether the interface is exposed to the internet or untrusted internal segments.Affected if The web interface is accessible to untrusted users, the reflected XSS can be triggered if they visit a specially crafted URL.
You are affected if AirWave is running and the installed version is lower than 8.2.12.0, regardless of web interface exposure, though exposure increases exploitability.
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 data8.2.12.0
Upgrade AirWave Management Platform to version 8.2.12.0 or later to obtain the patched version. This is a standard software update remediation with no known workarounds for production environments.
- 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-26967 — 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-26967 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