Orion PlatformApplication · Solarwinds

CVE-2022-36966

MEDIUM · 5.4 CVSS v3.1 Developing Published 2022-10-20
Fix available
A fix is available. Upgrade to 2020.2.6 or later.
See remediation →
60/100
Remediation priority · Elevated
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
Users with Node Management rights were able to view and edit all nodes due to Insufficient control on URL parameter causing insecure direct object reference (IDOR) vulnerability in SolarWinds Platform 2022.3 and previous.

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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-02.

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:< 2020.2.6= 2020.2.6= 2022.2= 2022.3

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

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 2020.2.6 or later
Fixed in 2020.2.6
Recommended fix Moderate confidence

SolarWinds Platform 2022.3.1 or later (consult SolarWinds release notes for exact first fixed build)

  1. 1. Identify the current installed version of SolarWinds Orion Platform via the Orion Administration page.
  2. 2. Navigate to the SolarWinds Customer Portal or official download page to obtain the fixed release.
  3. 3. Review the SolarWinds release notes for version 2022.3.1 or later for CVE-2022-36966 remediation details.
  4. 4. Before upgrading, backup the Orion database and configuration files.
  5. 5. Schedule a maintenance window as upgrades may require brief downtime.
  6. 6. Download and install the updated SolarWinds Platform version (2022.3.1 or later recommended).
  7. 7. After upgrade, verify that the IDOR vulnerability is resolved by confirming users with Node Management rights can no longer access nodes outside their assigned scope.
Caveat Standard upgrade considerations apply - review compatibility with existing extensions/plugins and ensure system requirements are met

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-36966 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