dbcve.org
Observability Self HostedApplication · Solarwinds

CVE-2026-28297

HIGH · 8.7 CVSS v3.1 Published 2026-03-26
Fix available
A fix is available. Upgrade to 2026.1.1 or later.
See remediation →
89/100
Remediation priority · High
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
SolarWinds Observability Self-Hosted 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 confidence

SolarWinds Observability Self-Hosted contains a stored (persistent) cross-site scripting vulnerability where malicious scripts can be injected and saved into the application, executing in the browsers of other users who view the compromised content.

MitigationApply vendor-provided security patch when released; implement input validation, output encoding, and Content Security Policy headers as compensating controls until patch is available.

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
Observability Self HostedApplication
Affected:< 2026.1.1

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
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SolarWinds Observability Self-Hosted is deployed
    Identify whether your environment runs the SolarWinds Observability Self-Hosted product. Check your inventory, deployment documentation, or running services for this application.
    Affected if The product is not present in your environment.
  2. Determine installed version
    Locate the version of SolarWinds Observability Self-Hosted currently running. Consult the administration console, installation logs, or product about page for the exact version number.
    Affected if The version cannot be determined or is not accessible.
  3. Compare version against affected range
    Take the installed version number and compare it to the affected range: versions prior to 2026.1.1 are vulnerable. If your version is lower than 2026.1.1 (for example, 2025.x, 2024.x, or earlier), you are running a vulnerable version.
    Affected if Your installed version is 2026.1.0 or earlier, or any version less than 2026.1.1.
  4. Identify user input and content display areas
    Audit the application for features that accept, store, and display user-supplied content to other users (such as dashboards, reports, annotations, custom fields, or configuration inputs). These are the potential injection points for stored XSS.
    Affected if The application stores and displays user input to other users and you are running a vulnerable version.

You are affected if SolarWinds Observability Self-Hosted is deployed and the installed version is any release prior to 2026.1.1, with user input areas that store and display content to other users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 2026.1.1 or later
Fixed in 2026.1.1
Interim mitigation

Apply vendor-provided security patch when released; implement input validation, output encoding, and Content Security Policy headers as compensating controls until patch is available.

Recommended fix Moderate confidence

2026.1.1 or later

  1. 1. Back up your current SolarWinds Observability Self-Hosted installation and database before proceeding with any upgrade.
  2. 2. Review the official SolarWinds Observability Self-Hosted upgrade documentation at documentation.solarwinds.com for version-specific upgrade procedures.
  3. 3. Upgrade your installation to version 2026.1.1 or later to resolve the stored XSS vulnerability.
  4. 4. After upgrading, verify that the web interface is functioning correctly and test that XSS protections are working as expected.
  5. 5. Monitor SolarWinds security advisories for any additional updates or patches.

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

Fix this in Observability Self Hosted Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28297 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2026-28297 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