CVE-2026-28322
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 Database Performance Analyzer was found to be affected by a stored cross-site scripting vulnerability, which when exploited, can lead to unintended script execution.
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 confidenceA stored cross-site scripting (XSS) vulnerability exists in SolarWinds Database Performance Analyzer. Attackers can inject malicious JavaScript code into data fields that are persisted in the application and rendered to other users, leading to unintended script execution in their browsers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Adjacent
- Complexity
- High
- Privileges
- High
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/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 SolarWinds Database Performance Analyzer installationLocate the DPA installation directory (common paths: C:\Program Files\SolarWinds\DPA on Windows or /opt/solarwinds/dpa on Linux). Verify the existence of DPA executable files or service.Affected if SolarWinds Database Performance Analyzer is present on the system
-
Determine installed DPA versionCheck the version of the installed DPA instance. On Windows, open Programs and Features or check the DPA service properties. On Linux, run: dpkg -l | grep -i dpa or rpm -qa | grep -i dpa. Alternatively, check the DPA installation directory for a version file or check the web interface login page for version information.Affected if The installed version is lower than the fixed version released for CVE-2026-28322 (version comparison required)
-
Verify web interface accessibilityConfirm that the DPA web-based management interface is accessible by accessing the application URL (default ports: 8127 or 8080). The stored XSS vulnerability requires the web interface to be reachable.Affected if The DPA web interface is accessible to users or attackers
-
Check if user data input modules are enabledIdentify which DPA modules allow user-supplied data to be stored and displayed. These typically include: custom query naming, alert descriptions, report names, or custom tags/notes attached to database monitoring objects. Review application configuration files in the DPA installation directory for enabled features.Affected if User input fields that persist data to the database and render it to other users are available in the application
Your environment is affected if SolarWwinds Database Performance Analyzer is installed, the web interface is accessible, and user-facing data input fields are enabled that store and render content to other users without proper encoding.
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 dataImplement strict input validation and output encoding for all user-supplied data before storage and rendering. Apply context-aware escaping when displaying stored data to users.
- Consultation6.0 h
- Implementation12.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28322 — 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-2026-28322 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