dbcve.org
Edgeconnect Sd Wan OrchestratorWeb browser · Arubanetworks

CVE-2025-37181

HIGH · 7.2 CVSS v3.1 Published 2026-01-14
Fix available
A fix is available. Upgrade to 9.5.6 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Vulnerabilities in the web-based management interface of EdgeConnect SD-WAN Orchestrator could allow an authenticated remote attacker to perform SQL injection attacks. Successful exploitation could allow an attacker to execute arbitrary SQL commands on the underlying database, potentially leading to unauthorized data access or data manipulation.

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 confidence

SQL injection vulnerabilities in the web-based management interface of EdgeConnect SD-WAN Orchestrator allow authenticated remote attackers to inject arbitrary SQL commands through unsanitized input fields, potentially enabling unauthorized data access or manipulation of the underlying database.

MitigationApply vendor-supplied patches when available; until then, implement input validation, use parameterized queries, restrict database privileges to least privilege, and consider deploying a WAF with SQL injection detection rules.

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
Edgeconnect Sd Wan OrchestratorWeb browser
Affected:>= 9.2.0, <= 9.2.10>= 9.3.0, <= 9.3.6>= 9.4.0, <= 9.4.4>= 9.5.0, < 9.5.6= 9.6.0

CVSS 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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if EdgeConnect web management interface is accessible
    Determine if the Orchestrator web UI is exposed and reachable on the network. Check if TCP ports typically used for the web interface (such as 443, 8443, or vendor-defined ports) are open and responding.
    Affected if The web-based management interface is exposed and accessible to network attackers, enabling them to reach the login page and attempt authentication.
  2. Locate the installed version of EdgeConnect SD-WAN Orchestrator
    Access the Orchestrator web interface login page or admin dashboard, where version information is typically displayed. Alternatively, check the system console or CLI for a 'show version' or 'version' command that displays the running software version.
    Affected if Unable to determine the version, making it impossible to compare against the affected ranges.
  3. Compare the installed version against affected ranges
    Match the identified version to the following affected ranges: 9.2.0 through 9.2.10, 9.3.0 through 9.3.6, 9.4.0 through 9.4.4, 9.5.0 through 9.5.5, or exactly version 9.6.0. Any version falling within or matching these ranges is vulnerable.
    Affected if The installed version falls within or matches any of the following ranges: 9.2.0-9.2.10, 9.3.0-9.3.6, 9.4.0-9.4.4, 9.5.0-9.5.5, or equals 9.6.0.
  4. Confirm authentication to the web interface is possible
    Verify that valid user credentials exist for the Orchestrator web management interface. This includes local admin accounts, LDAP-integrated accounts, or other authentication methods supported by the platform.
    Affected if User accounts exist that can authenticate to the web interface, allowing the SQL injection to be exploited by any authenticated user with access to input fields.

A user is affected if the EdgeConnect SD-WAN Orchestrator web management interface is accessible, a valid user can authenticate to it, and the installed software version falls within the listed vulnerable ranges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 9.5.6 or later
Fixed in 9.5.6
Interim mitigation

Apply vendor-supplied patches when available; until then, implement input validation, use parameterized queries, restrict database privileges to least privilege, and consider deploying a WAF with SQL injection detection rules.

Recommended fix Moderate confidence

Upgrade to version 9.5.6 or later for the 9.5.x branch; for older branches, upgrade to the latest version in that branch that includes the security fix (9.2.11+, 9.3.7+, 9.4.5+, or migrate to 9.5.6+)

  1. 1. Identify the current installed version of EdgeConnect SD-WAN Orchestrator from the web-based management interface or system information.
  2. 2. Determine which version branch you are currently running (9.2.x, 9.3.x, 9.4.x, or 9.5.x).
  3. 3. Download the appropriate fixed version from HPE support portal at support.hpe.com.
  4. 4. Schedule a maintenance window as the upgrade will require a brief service interruption.
  5. 5. Back up the current configuration and database as a precautionary measure.
  6. 6. Follow the standard EdgeConnect SD-WAN Orchestrator upgrade procedure documented in the HPE administration guide.
  7. 7. After upgrade, verify the new version is running and test that the web-based management interface is functional.
  8. 8. Confirm the SQL injection vulnerability is resolved by verifying the fix is applied.
Caveat Standard minor version upgrades typically have minimal breaking changes; review HPE release notes for any configuration or behavioral changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Edgeconnect Sd Wan Orchestrator Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-37181 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-37181 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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