CVE-2026-28298
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 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 confidenceA stored cross-site scripting (XSS) vulnerability in SolarWinds Observability Self-Hosted allows attackers to inject malicious scripts that are permanently stored on the server and executed in the browsers of users who access the affected functionality.
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< 2026.1.1CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:L/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Check the installed version of SolarWinds Observability Self-HostedAccess the administration interface or run the version command provided by SolarWinds to retrieve the current product versionAffected if The installed version is lower than 2026.1.1 (for example, 2025.x.x or earlier)
-
Identify if user-generated content storage features are enabledReview the application configuration settings or administration panel for features that allow users to store and display custom content, such as custom dashboards, alerts, or notesAffected if Features that store and render user-supplied content are active and accessible to users
-
Verify if the application processes and displays stored user input without sanitizationLog in as a standard user and attempt to inject a harmless test script into a field that stores data for later display (such as a dashboard label, alert description, or custom field)Affected if The application renders the stored input as raw HTML or script content without encoding or sanitization when viewed by other users
-
Review application logs for XSS-related security eventsExamine the application and web server logs for any entries indicating XSS attempts or malformed script content in stored fieldsAffected if Logs show unescaped script tags or HTML elements being stored in user-controlled fields
You are affected if your SolarWinds Observability Self-Hosted version is below 2026.1.1 and your environment allows users to store content that gets rendered without output 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.
dbcve · scoped2026.1.1
Implement strict input validation and proper output encoding on all user-supplied data, sanitize existing stored data, and consider implementing Content Security Policy (CSP) headers to mitigate XSS execution.
2026.1.1
- Upgrade SolarWinds Observability Self-Hosted to version 2026.1.1 or later to resolve the stored XSS vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation12.0 h
- Implementation32.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $19,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28298 — 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-28298 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