CVE-2022-36960
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 · uneditedSolarWinds Platform was susceptible to Improper Input Validation. This vulnerability allows a remote adversary with valid access to SolarWinds Web Console to escalate user privileges.
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 confidenceSolarWinds Platform contains an improper input validation vulnerability in its Web Console component. An authenticated remote attacker with valid credentials can exploit this flaw to escalate their privileges to higher permission levels within the application.
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< 2020.2.6= 2020.2.6= 2022.2= 2022.3CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify SolarWinds Orion Platform installationLocate the SolarWinds Orion Platform installation directory or check installed programs on the server hosting the SolarWinds application.Affected if SolarWinds Orion Platform is not installed on the system.
-
Determine installed Orion Platform versionAccess the SolarWinds Web Console and navigate to the About page (typically at /About.aspx) or use the Orion Diagnostic Analyzer (ODA) tool to retrieve the exact version number.Affected if The installed version matches any of these: < 2020.2.6, 2020.2.6, 2022.2, or 2022.3.
-
Verify Web Console component statusCheck if the SolarWinds Web Console is accessible and enabled by attempting to reach the web interface URL or reviewing IIS/site configuration settings.Affected if The Web Console is enabled and accessible.
-
Review user account privilegesExamine the account used for the detection to determine if it has valid credentials for the SolarWinds platform.Affected if Valid credentials exist for an authenticated user account within the platform.
A user is affected if the SolarWinds Orion Platform version falls within the vulnerable range (2020.2.6, 2022.2, or 2022.3) AND the Web Console component is enabled with valid user accounts present.
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.
From vendor data2020.2.6
Apply the vendor-supplied patch for CVE-2022-36960 and ensure all user inputs in the Web Console are properly validated using allowlist validation and context-aware sanitization.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.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 $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36960 — 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-2022-36960 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