CVE-2021-35229
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 · uneditedCross-site scripting vulnerability is present in Database Performance Monitor 2022.1.7779 and previous versions when using a complex SQL query
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 · moderate confidenceCross-site scripting (XSS) vulnerability in SolarWinds Database Performance Monitor allows injection of malicious JavaScript through complex SQL queries. When the SQL query results are displayed in the web interface, unsanitized input enables script execution in the context of other users' sessions.
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.2<= 2022.1.7779CVSS 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.
-
Confirm Database Performance Monitor installationLocate the SolarWinds Database Performance Monitor installation directory, typically under Program Files\SolarWinds\ or check Windows Services for 'SolarWinds Database Performance Monitor' serviceAffected if The product is not installed - not affected; if installed, continue to version check
-
Identify installed DPM versionCheck the product version through the web interface (typically at /admin/about or /help/about), or locate a version file in the installation directoryAffected if Version is 2022.1.7779 or later - not affected; version is below 2022.2 (for DPA) or 2022.1.7779 (for DPM) - potentially affected
-
Verify web interface accessibilityAccess the DPM web console URL and confirm it is reachable (default ports 8080 or 8443 for the web interface)Affected if Web interface is not accessible or not in use - vulnerability cannot be exploited
-
Check if SQL query display feature is usedNavigate to the query results or monitoring views in the web interface where SQL query results are displayedAffected if SQL query results are displayed in the web interface - attack vector is present; if queries are never displayed, exploitation is not feasible
Environment is affected if SolarWinds Database Performance Monitor/Database Performance Analyzer is installed with a version below 2022.2 (DPA) or 2022.1.7779 (DPM) and the web interface with SQL query display functionality is accessible.
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.2
Upgrade to Database Performance Monitor version 2022.1.7779 or later; alternatively, implement output encoding and input validation on all SQL query display paths.
Database Performance Analyzer 2022.2 or later / Database Performance Monitor 2022.2 or later
- Identify which Solarwinds product is affected: Database Performance Analyzer or Database Performance Monitor
- Check the current installed version of the affected product
- For Database Performance Analyzer: Upgrade to version 2022.2 or later
- For Database Performance Monitor: Upgrade to version 2022.2 or later (version after 2022.1.7779)
- Verify the upgrade was successful and the version is now at 2022.2 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-35229 — 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-2021-35229 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