CVE-2015-1390
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 · uneditedAruba AirWave before 8.0.7 allows XSS attacks agsinat an administrator.
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 confidenceAruba AirWave before version 8.0.7 contains a stored Cross-Site Scripting (XSS) vulnerability in its web interface. An attacker can inject malicious JavaScript code that executes within an administrator's browser session when they access the compromised page, potentially allowing session hijacking or administrative action manipulation.
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.0.0.0, < 8.0.7CVSS 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.
-
Identify installed AirWave versionLog into the AirWave web interface and navigate to Home > About, or use the CLI command 'show version' to retrieve the firmware/software version.Affected if The installed version is 8.0.0.0 through 8.0.6.x (inclusive), meaning it falls within >= 8.0.0.0 and < 8.0.7.
-
Confirm web interface is accessibleAttempt to reach the AirWave web interface over HTTP/HTTPS from a browser.Affected if The web interface is exposed and accepts authentication, as the XSS payload executes when an administrator accesses the compromised page.
-
Review application logs for XSS indicatorsExamine AirWave system logs and web server logs for suspicious script tags, JavaScript function calls, or encoded payloads that may indicate attempted or successful XSS injection.Affected if Unusual or malicious script content is found stored in the application or logged entries.
-
Audit user-created content in the interfaceReview any user-configurable fields such as device names, group descriptions, template names, or other stored parameters where an attacker could have injected malicious code.Affected if Stored content contains unsanitized HTML or JavaScript that would execute in an administrator's browser session.
You are affected if your AirWave installation version is 8.0.0.0 or higher but lower than 8.0.7, and the web interface with administrative access is in use.
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.
dbcve · scoped8.0.7
Upgrade Aruba AirWave to version 8.0.7 or later to remediate this vulnerability.
8.0.7
- Upgrade Aruba AirWave to version 8.0.7 or later to resolve the XSS vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1390 — 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-1390 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