dbcve.org
Orion PlatformApplication · Solarwinds

CVE-2022-47507

HIGH · 7.2 CVSS v3.1 Published 2023-02-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
SolarWinds Platform was susceptible to the Deserialization of Untrusted Data. This vulnerability allows a remote adversary with Orion admin-level account access to SolarWinds Web Console 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

SolarWinds Platform contains a deserialization vulnerability where untrusted data is processed without proper validation. An attacker with admin-level credentials to the Orion Web Console can exploit this to achieve arbitrary command execution on the underlying system.

MitigationApply SolarWinds security patches/hotfixes for this vulnerability. Immediately restrict Orion Web Console access to only necessary admin personnel, enforce least-privilege principles, and implement network segmentation to limit exposure.

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:= 2022.4.1

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 installation
    On the SolarWinds server, open the SolarWinds Orion Platform and navigate to Settings > All Settings > About Orion, or run 'Get-SolarWindsProductInfo' via PowerShell if available. Alternatively, check Add/Remove Programs for 'SolarWinds Orion Platform' entry.
    Affected if SolarWinds Orion Platform is NOT installed - not affected. If installed, proceed to version check.
  2. Verify the exact installed version is 2022.4.1
    Locate the version number from the About page or installation metadata. Compare it precisely to '2022.4.1' - note that only this exact version is affected, not a range.
    Affected if The installed version is exactly 2022.4.1 - potentially affected. Versions before or after this specific release are NOT affected by this CVE.
  3. Confirm Orion Web Console is enabled and accessible
    Check if the Orion Web Console service (usually 'SolarWinds Orion Web Console' or 'Orion Website' in IIS) is running. Verify the web application is accessible at the configured URL (default port 443 or 8080).
    Affected if Orion Web Console is running and accessible - the vulnerability can be exploited. If the web console is disabled or not installed, the attack surface does not exist.
  4. Identify admin-level accounts on the Orion Web Console
    Log into the Orion Web Console as an administrator and navigate to Settings > All Settings > User Accounts, or check the Orion database for accounts with 'Administrator' role permissions.
    Affected if Admin-level accounts exist and are accessible - an attacker with these credentials could exploit the vulnerability. The CVE requires admin credentials to be usable.
  5. Assess network exposure of the Orion Web Console
    Review firewall rules, IIS bindings, and network ACLs to determine if the Orion Web Console is accessible from outside the trusted network. Check if it listens on 0.0.0.0 versus localhost only.
    Affected if The Orion Web Console is exposed to untrusted networks (internet or DMZ) - exploitation is more likely in this configuration.

A user is affected ONLY if SolarWinds Orion Platform version 2022.4.1 is installed, the Orion Web Console is enabled and accessible, and an attacker can obtain or already has admin-level credentials to the Orion Web Console.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply SolarWinds security patches/hotfixes for this vulnerability. Immediately restrict Orion Web Console access to only necessary admin personnel, enforce least-privilege principles, and implement network segmentation to limit exposure.

Recommended fix Moderate confidence

Orion Platform 2022.4.2 or later

  1. 1. Log in to the SolarWinds Customer Portal at support.solarwinds.com
  2. 2. Navigate to the Orion Platform product page and locate version 2022.4.2 or later
  3. 3. Download the upgrade package for the recommended stable release
  4. 4. Review the upgrade prerequisites in the SolarWinds documentation
  5. 5. Create a full backup of the Orion database and configuration
  6. 6. Schedule a maintenance window and stop all Orion services
  7. 7. Run the upgrade installer following the standard SolarWinds upgrade procedure
  8. 8. After upgrade completes, verify all Orion services start successfully
Caveat Review upgrade documentation for potential impacts to custom integrations, third-party plugins, or migration requirements between major versions

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

Fix this in Orion Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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