CVE-2023-37423
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 · uneditedVulnerabilities 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 confidenceStored XSS vulnerability in EdgeConnect SD-WAN Orchestrator's web-based management interface allows authenticated attackers to inject malicious scripts that execute in the browsers of administrative users viewing the affected content.
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.0.0, <= 9.0.5>= 9.1.0, <= 9.1.7>= 9.2.0, <= 9.2.5= 9.3.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed EdgeConnect SD-WAN Orchestrator versionAccess the web-based management interface and navigate to the version or about section, typically found in the system settings or help menu. Alternatively, check the orchestrator's system information page or administrative console for the exact version number.Affected if The displayed version falls within 9.0.0-9.0.5, 9.1.0-9.1.7, 9.2.0-9.2.5, or 9.3.0 exactly.
-
Confirm the web-based management interface is enabledVerify that the web management interface is accessible by attempting to reach the orchestrator's web URL. Check the orchestration service status to confirm it is running and accepting web connections.Affected if The web management interface is active and reachable over the network.
-
Identify authenticated user access pathsDetermine whether any user accounts with access to the management interface exist. Review the user management or authentication settings to confirm the presence of at least one account with administrative or editor privileges.Affected if There is at least one authenticated user account configured with access to the management interface.
-
Review input handling in management interface fieldsExamine the management interface for fields that accept user-supplied data and store it for later display. Common locations include device names, descriptions, policy labels, or configuration notes. Inspect whether these fields display stored data back to users without visible sanitization indicators.Affected if The interface contains fields that persist user input for display to other administrative users.
You are affected if your EdgeConnect SD-WAN Orchestrator version is within 9.0.0-9.0.5, 9.1.0-9.1.7, 9.2.0-9.2.5, or exactly 9.3.0, and the web-based management interface is accessible with at least one authenticated user account.
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 · scopedApply vendor patch when available; implement input validation and output encoding for all user-supplied data in the management interface; consider CSP headers as defense-in-depth.
Upgrade to the next maintenance release in your current branch (9.0.6+, 9.1.8+, 9.2.6+, or 9.3.1+)
- 1. Identify the current EdgeConnect SD-WAN Orchestrator version in use from the web management interface or CLI
- 2. Based on the current version, upgrade to the next available maintenance release that addresses the vulnerability
- 3. For 9.0.x branch: upgrade to 9.0.6 or later
- 4. For 9.1.x branch: upgrade to 9.1.8 or later
- 5. For 9.2.x branch: upgrade to 9.2.6 or later
- 6. For 9.3.0: upgrade to 9.3.1 or later
- 7. After upgrade, verify the web-based management interface is accessible and functional
- 8. Test that the XSS vulnerability is no longer present by attempting to inject script content in input fields that were previously vulnerable
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-2023-37423 — 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-2023-37423 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