dbcve.org
Orion PlatformApplication · Solarwinds

CVE-2022-36963

HIGH · 7.2 CVSS v3.1 Published 2023-04-21
Fix available
A fix is available. Upgrade to 2023.2 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
The SolarWinds Platform was susceptible to the Command Injection Vulnerability. This vulnerability allows a remote adversary with a valid SolarWinds Platform admin account to execute arbitrary commands.

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

A command injection vulnerability exists in the SolarWinds Platform that allows a remote attacker with a valid administrator account to execute arbitrary commands on the underlying system. The vulnerability stems from improper input validation in the Platform, enabling authenticated users to inject OS-level commands beyond their intended scope.

MitigationApply the vendor-supplied patch for CVE-2022-36963 immediately. Additionally, audit all admin-level accounts for compromise, enforce strong credential policies, limit admin access to dedicated secure workstations, and monitor for suspicious command execution activity.

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
Orion PlatformApplication
Affected:< 2023.2

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. Confirm SolarWinds Orion Platform is installed
    Inspect the system for SolarWinds Orion Platform installation directories or check Windows Programs and Features for 'SolarWinds Orion' or 'SolarWinds Platform' entries
    Affected if SolarWinds Orion Platform is found on the system
  2. Determine installed platform version
    Access the SolarWinds web interface and navigate to the About page (typically Settings > All Settings > About) or check the Orion installer information, then record the exact version number
    Affected if The version is anything less than 2023.2 (e.g., 2023.1.x, 2022.x, or earlier releases)
  3. Verify administrator account existence
    Check for active administrator-level accounts in SolarWinds Orion via the web UI under Settings > All Settings > User Accounts, or enumerate local Windows accounts with administrative privileges on the Orion server
    Affected if At least one valid administrator account exists in the SolarWinds system (this account type is required for exploitation)
  4. Assess network exposure of Orion management interface
    Review firewall rules and network configuration to determine if the SolarWinds web console is accessible from untrusted networks
    Affected if The Orion web interface is exposed to the internet or untrusted internal segments without proper network segmentation

The environment is affected if SolarWinds Orion Platform is installed with a version below 2023.2 AND an administrator account exists in the system, as both conditions are required for successful command injection exploitation.

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 2023.2 or later
Fixed in 2023.2
Interim mitigation

Apply the vendor-supplied patch for CVE-2022-36963 immediately. Additionally, audit all admin-level accounts for compromise, enforce strong credential policies, limit admin access to dedicated secure workstations, and monitor for suspicious command execution activity.

Recommended fix High confidence

SolarWinds Platform 2023.2 or later

  1. 1. Create a complete backup of the SolarWinds Orion Platform database and configuration
  2. 2. Review the SolarWinds Platform 2023.2 release notes and upgrade prerequisites at the official documentation portal
  3. 3. Download the SolarWinds Platform 2023.2 (or later) upgrade package from the official SolarWinds customer portal
  4. 4. Execute the upgrade following the official SolarWinds upgrade documentation for the Orion Platform
  5. 5. After upgrade completion, verify the SolarWinds services are running correctly
  6. 6. Confirm the version number reflects 2023.2 or later in the web console
Caveat Review 2023.2 release notes for any configuration changes or deprecated features that may affect your deployment

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

Fix this in Orion Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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