CVE-2025-27084
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 vulnerability in the Captive Portal of an AOS-10 GW and AOS-8 Controller/Mobility Conductor could allow a remote attacker to conduct a reflected cross-site scripting (XSS) attack. Successful exploitation could enable the attacker to execute arbitrary script code in the victim's browser within the context of the affected 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 · moderate confidenceA reflected cross-site scripting (XSS) vulnerability exists in the Captive Portal component of Aruba AOS-10 GW and AOS-8 Controller/Mobility Conductor. Attackers can craft malicious URLs containing script payloads that get reflected back to users' browsers when they access the Captive Portal, allowing execution of arbitrary JavaScript within the context of the affected 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>= 8.10.0.0, < 8.10.0.16>= 8.12.0.0, < 8.12.0.4>= 10.4.0.0, < 10.4.1.7>= 10.7.0.0, < 10.7.1.1CVSS 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.
-
Confirm Captive Portal is enabledLog into the Aruba controller/mobility conductor and run the command to display Captive Portal status, such as 'show captive-portal status' or check the Captive Portal configuration via 'show running-config | include captive-portal'Affected if Captive Portal is actively enabled or configured on the device; if disabled, the XSS vector does not apply
-
Identify installed software versionRun 'show version' on the controller CLI to retrieve the exact AOS version number (for AOS-8) or 'show version detailed' for AOS-10Affected if The installed version falls within any of these ranges: >= 8.10.0.0 and < 8.10.0.16; >= 8.12.0.0 and < 8.12.0.4; >= 10.4.0.0 and < 10.4.1.7; >= 10.7.0.0 and < 10.7.1.1
-
Determine device role in deploymentVerify the device role by running 'show controller-ip' or checking the topology to confirm if the device functions as a Gateway (GW), Controller, or Mobility ConductorAffected if The device is deployed as an AOS-10 Gateway, AOS-8 Controller, or Mobility Conductor with Captive Portal enabled and a vulnerable version installed
-
Verify Captive Portal profile configurationReview the Captive Portal profile settings using commands like 'show captive-portal profile <profile_name>' to confirm the portal is actively serving authentication pagesAffected if A Captive Portal profile exists and is assigned to SSIDs, user roles, or VLANs, meaning users can be redirected to the portal
The environment is affected if Captive Portal is enabled on an Aruba AOS-8 or AOS-10 device running a version within the affected ranges listed above.
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.10.0.168.12.0.410.4.1.7
Apply the vendor-supplied patch or upgrade to a fixed software version. If immediate patching is not possible, implement URL parameter validation and output encoding on Captive Portal responses as a temporary mitigation.
Upgrade to 8.10.0.16 (for 8.10.x branch), 8.12.0.4 (for 8.12.x branch), 10.4.1.7 (for 10.4.x branch), or 10.7.1.1 (for 10.7.x branch)
- Identify the current ArubaOS version by checking the controller, Mobility Conductor, or Gateway web interface or running 'show version' in CLI
- Determine which version branch you are running (8.10.x, 8.12.x, 10.4.x, or 10.7.x)
- Download the appropriate fixed release from HPE Aruba support portal (support.hpe.com): for 8.10.x upgrade to 8.10.0.16, for 8.12.x upgrade to 8.12.0.4, for 10.4.x upgrade to 10.4.1.7, for 10.7.x upgrade to 10.7.1.1
- Review the Aruba upgrade guide for your platform to ensure all prerequisites are met
- Before upgrading in production, test the upgrade in a non-production environment to verify stability
- Upload the new firmware to the device using the web interface or CLI (copy command)
- Initiate the upgrade via CLI ('upgrade-software') or web interface
- After upgrade completes, verify the new version is running with 'show version'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.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,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27084 — 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-2025-27084 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