dbcve.org
Edgeconnect Sd Wan OrchestratorWeb browser · Arubanetworks

CVE-2023-37422

MEDIUM · 5.4 CVSS v3.1 Published 2023-08-22
Fix available
A fix is available. Upgrade to after 9.2.5 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 conduct a stored cross-site scripting (XSS) attack against an administrative user of the interface. A successful exploit allows an attacker to execute arbitrary script code in a victim's browser in 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 confidence

This is a stored cross-site scripting (XSS) vulnerability in the web-based management interface of EdgeConnect SD-WAN Orchestrator. An authenticated attacker can inject malicious script code that gets persisted in the application (likely through a form field or configuration parameter), which then executes in the browser of administrative users who view the affected content. The CVSS 5.4 indicates network accessibility, low attack complexity, and user interaction required.

MitigationApply vendor patches when available; until then, implement strict input validation and output encoding on all user-supplied data in the management interface, and consider implementing Content Security Policy (CSP) headers to mitigate script execution.

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.0.0, <= 9.0.5>= 9.1.0, <= 9.1.7>= 9.2.0, <= 9.2.5= 9.3.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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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

  1. Verify EdgeConnect SD-WAN Orchestrator web interface is accessible
    Attempt to access the management interface via HTTPS on the expected port (typically 443 or 8443). If the login page loads, the web interface is exposed.
    Affected if The web-based management interface is reachable over the network.
  2. Determine the installed Orchestrator version
    Log into the web management interface and navigate to the system information or about page. Alternatively, access the Orchestrator CLI and run the command to display the software version (e.g., 'show version' or 'show system info').
    Affected if The displayed version falls within any of these ranges: 9.0.0-9.0.5, 9.1.0-9.1.7, 9.2.0-9.2.5, or 9.3.0.
  3. Confirm administrative accounts exist
    Check if there are any user accounts with administrative privileges configured in the Orchestrator. Navigate to the user management or administration section of the web interface, or use the CLI command to list admin users.
    Affected if Administrative users are configured and can log into the management interface.
  4. Identify form inputs or configuration parameters that accept user-supplied data
    In the management interface, review forms where an authenticated user can submit data, such as device names, descriptions, policy settings, or custom fields. These are potential injection points for stored XSS.
    Affected if The interface accepts and persists user input through form fields or configuration parameters that are displayed back to other users.

Your environment is affected if the EdgeConnect SD-WAN Orchestrator web interface is accessible and the installed version is 9.0.0 through 9.0.5, 9.1.0 through 9.1.7, 9.2.0 through 9.2.5, or exactly 9.3.0.

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.

From vendor data
Upgrade available Upgrade to a release after 9.2.5
Interim mitigation

Apply vendor patches when available; until then, implement strict input validation and output encoding on all user-supplied data in the management interface, and consider implementing Content Security Policy (CSP) headers to mitigate script execution.

Fix this in Edgeconnect Sd Wan Orchestrator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

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