CVE-2022-36965
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 · uneditedInsufficient sanitization of inputs in QoE application input field could lead to stored and Dom based XSS attack. This issue is fixed and released in SolarWinds Platform (2022.3.0).
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 confidenceInsufficient input sanitization in the QoE (Quality of Experience) application input field allows attackers to inject malicious scripts that execute in users' browsers. This vulnerability enables both stored XSS (persisting malicious scripts in the database) and DOM-based XSS (manipulating client-side script execution), posing risks to user sessions, credentials, and potential application compromise.
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< 2022.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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check installed SolarWinds Platform versionAccess the platform's version information through the web interface (About page) or by reviewing the installation manifestAffected if Version is below 2022.3.0 (any version prior to 2022.3.0)
-
Confirm QoE application module is presentVerify whether the Quality of Experience (QoE) application feature is installed or enabled in your SolarWinds Platform deploymentAffected if QoE module exists and version is below 2022.3.0
-
Inspect QoE input fields for anomalous contentIf you have access to the QoE application interface, review any input fields where users submit data (such as application names, descriptions, or configuration parameters)Affected if Unexpected script tags or HTML attributes are found in QoE input fields
-
Review web server logs for XSS patternsExamine access and application logs for suspicious patterns involving script tags, javascript:, or event handlers in QoE-related request parametersAffected if Malicious script injection attempts are logged in QoE endpoints
You are affected if your SolarWinds Platform version is below 2022.3.0 and the QoE application module is enabled or has been used in your environment.
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 · scoped2022.3.0
Upgrade to SolarWinds Platform version 2022.3.0 or later, which contains the fix for proper input sanitization. Prioritize this upgrade given the stored XSS component, which affects all users viewing the injected content.
SolarWinds Platform 2022.3.0
- 1. Create a full backup of your current SolarWinds Platform configuration and database
- 2. Download the SolarWinds Platform 2022.3.0 installer from the official SolarWinds customer portal
- 3. Review the official upgrade documentation for SolarWinds Platform 2022.3.0 for specific prerequisites
- 4. Run the installer on the SolarWinds Platform server and follow the upgrade wizard
- 5. After upgrade completes, verify all SolarWinds services are running
- 6. Log into the SolarWinds Platform web interface
- 7. Navigate to the QoE application and test the input field to confirm the XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36965 — 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-36965 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