CVE-2025-37160
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 broken access control (BAC) vulnerability in the web-based management interface could allow an authenticated remote attacker with low privileges to view sensitive information. Successful exploitation of this vulnerability could enable the attacker to disclose sensitive data.
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 confidenceThis is a Broken Access Control (BAC) vulnerability in a web-based management interface where low-privilege authenticated users can view sensitive information they should not have access to. The application properly authenticates users but fails to properly enforce authorization checks to restrict low-privilege users from accessing sensitive data endpoints or functions.
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>= 10.10.0000, < 10.10.1170>= 10.13.0000, < 10.13.1101>= 10.14.0000, < 10.14.1060>= 10.15.0000, < 10.15.1030>= 10.16.0000, < 10.16.1001CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Check ArubaOS CX versionRun 'show version' command on the switch CLI or check via web management interface system information pageAffected if Installed version falls within any of these ranges: 10.10.0000-10.10.1169, 10.13.0000-10.13.1100, 10.14.0000-10.14.1059, 10.15.0000-10.15.1029, 10.16.0000-10.16.1000
-
Verify web-based management interface is enabledCheck CLI output of 'show http-server' or 'show web-ui status' to confirm the web management interface is activeAffected if The web management interface is enabled and accessible to users
-
Identify configured user roles and privilege levelsRun 'show aaa authorization' and 'show role' commands to list all configured roles and their permission levelsAffected if Multiple roles exist with varying privilege levels, including low-privilege roles (such as 'operator' or 'readonly')
-
Inspect role-based access control (RBAC) configurationsRun 'show role <role_name>' for each role to examine permitted commands and API endpoints, particularly for sensitive data accessAffected if Roles permit access to sensitive information endpoints without proper authorization checks
-
Test low-privilege user access to sensitive endpointsLog in with a low-privilege user account and attempt to access endpoints that should be restricted (such as system configuration, credentials, or audit logs)Affected if Low-privilege authenticated users can view sensitive data they are not authorized to access
The environment is affected if ArubaOS CX version is within the affected ranges AND the web management interface is enabled AND low-privilege users can access sensitive information beyond their authorized scope.
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 · scoped10.10.117010.13.110110.14.1060
Implement proper role-based access control (RBAC) checks on all sensitive data endpoints to ensure low-privilege users cannot access information beyond their authorized scope. Conduct a comprehensive access control audit across the management interface.
Upgrade to 10.10.1170 (for 10.10 branch), 10.13.1101 (for 10.13 branch), 10.14.1060 (for 10.14 branch), or 10.15.1030 (for 10.15 branch)
- Identify your current ArubaOS CX version using 'show version' in the CLI
- Determine which version branch you are on (10.10.x, 10.13.x, 10.14.x, or 10.15.x)
- Download the appropriate fixed firmware version from the HPE Aruba support portal (support.hpe.com)
- Transfer the firmware to the switch using 'copy tftp://<server>/<file> system:secondary'
- Schedule a maintenance window as upgrades may cause brief network interruption
- Execute the upgrade using 'boot system secondary' command
- Verify the upgrade was successful with 'show version' and confirm the version matches the fixed release
- Restart the switch if required to complete the upgrade process
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2025-37160 — 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-37160 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