CVE-2025-37184
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 exists in an Orchestrator service that could allow an unauthenticated remote attacker to bypass multi-factor authentication requirements. Successful exploitation could allow an attacker to create an admin user account without the necessary multi-factor authentication, thereby compromising the integrity of secured access to the system.
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 confidenceAn unauthenticated remote attacker can bypass multi-factor authentication in an Orchestrator service, allowing them to create an admin user account without completing MFA verification. This effectively grants full administrative access to the system without proper identity verification.
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>= 9.2.0, <= 9.2.10>= 9.3.0, < 9.3.6>= 9.4.0, < 9.4.3>= 9.5.0, < 9.5.6= 9.6.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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 the Orchestrator software versionLog into the Orchestrator admin interface and navigate to Dashboard > System > Software, or use the CLI command 'show version' if you have CLI access. The version number will be displayed prominently.Affected if The installed version matches one of the affected ranges: 9.2.0 through 9.2.10, 9.3.0 through 9.3.5, 9.4.0 through 9.4.2, 9.5.0 through 9.5.5, or exactly 9.6.0
-
Verify whether remote administrative access is enabledIn the Orchestrator web interface, go to Configuration > Security > Access Control or Configuration > Administration > Remote Access. Look for settings that enable remote admin login over HTTP/HTTPS from external networks.Affected if Remote administrative access is enabled and the Orchestrator is reachable from untrusted networks
-
Confirm MFA enforcement status for administrator accountsNavigate to Configuration > Security > Multi-Factor Authentication or Configuration > Administration > Users. Verify whether MFA is globally enforced for all admin accounts and that the enforcement cannot be bypassed during user creation.Affected if MFA is not enforced, or enforcement can be bypassed when creating new admin users
A user is affected if their Orchestrator version falls within the listed vulnerable ranges AND remote administrative access is enabled, allowing unauthenticated attackers to potentially create admin accounts without MFA verification.
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 · scoped9.3.69.4.39.5.6
Apply vendor-provided patches immediately to address the MFA bypass vulnerability. Until patched, consider disabling remote administrative access to the Orchestrator service or implementing additional network-level access controls.
Upgrade to 9.3.6 (if on 9.3.x), 9.4.3 (if on 9.4.x), or 9.5.6 (if on 9.5.x) - or migrate to the latest available release in your supported branch
- 1. Access the EdgeConnect SD-WAN Orchestrator administrative interface
- 2. Navigate to System > Administration > Software Management or similar upgrade section
- 3. Download the appropriate patched version from HPE support portal (support.hpe.com)
- 4. Create a backup of the current configuration
- 5. Upload and install the patched software version (9.3.6, 9.4.3, or 9.5.6 depending on your current branch)
- 6. Verify the upgrade completed successfully
- 7. Confirm MFA enforcement is functioning properly by testing authentication flows
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-37184 — 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-37184 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