dbcve.org
Edgeconnect Sd Wan OrchestratorWeb browser · Arubanetworks

CVE-2025-37182

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 · high confidence

SQL injection vulnerability in EdgeConnect SD-WAN Orchestrator's web-based management interface allows authenticated remote attackers to inject arbitrary SQL commands through unsanitized input fields, potentially exposing or manipulating database contents.

MitigationImplement parameterized queries or prepared statements for all database interactions; validate and sanitize all user inputs; apply vendor patches when available; consider WAF deployment as compensating control.

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 installed EdgeConnect version
    Check the Orchestrator Appliance management console or use the CLI command 'show version' to display the installed software version
    Affected if The displayed version falls within 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
  2. Confirm web management interface is enabled
    Access the Orchestrator admin panel via HTTPS on port 443 or check configuration via CLI for web interface status using 'show webui status'
    Affected if The web management interface is active and reachable on the network
  3. Verify authentication is configured
    Check if local or remote authentication (RADIUS/TACACS+) is enabled for the Orchestrator web interface by reviewing authentication settings in the admin console
    Affected if User authentication is configured for the web interface (authentication is required for exploitation, so this confirms the attack surface exists)

You are affected if your Orchestrator runs an affected version listed above AND the web-based management interface with authentication is enabled and accessible on your network.

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

Implement parameterized queries or prepared statements for all database interactions; validate and sanitize all user inputs; apply vendor patches when available; consider WAF deployment as compensating control.

Recommended fix Moderate confidence

Upgrade to version 9.2.11 or later (for 9.2.x branch), 9.3.7 or later (for 9.3.x branch), 9.4.5 or later (for 9.4.x branch), or 9.5.6 or later (for 9.5.x branch)

  1. 1. Identify the current installed version of EdgeConnect SD-WAN Orchestrator
  2. 2. Determine which version branch (9.2.x, 9.3.x, 9.4.x, or 9.5.x) is currently in use
  3. 3. Plan upgrade to the next available release in the same version branch that is beyond the last affected version
  4. 4. Review HPE support documentation at support.hpe.com for upgrade procedures specific to the EdgeConnect SD-WAN Orchestrator
  5. 5. Perform a backup of the current configuration before upgrading
  6. 6. Execute the upgrade following HPE's documented upgrade process
  7. 7. Verify the upgrade was successful and the SQL injection vulnerability is resolved
Caveat Review HPE release notes for any known issues or breaking changes between your current version and the target version before upgrading

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

Fix this in Edgeconnect Sd Wan Orchestrator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-37182 — 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-37182 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