Observability Self HostedApplication · Solarwinds

CVE-2025-26391

MEDIUM · 5.4 CVSS v3.1 Published 2025-11-18
Fix available
A fix is available. Upgrade to 2025.4.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 XSS Vulnerability. The SolarWinds Platform was susceptible to a XSS vulnerability that affects user-created URL fields. This vulnerability requires authentication from a low-level account.

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 Cross-Site Scripting (XSS) vulnerability in user-created URL fields. An attacker with low-level authentication can inject malicious scripts into URL parameters that are not properly sanitized when rendered, allowing execution in the context of other users' sessions.

MitigationImplement context-aware output encoding and validation for URL fields, enforce Content Security Policy headers, and apply vendor-supplied patches when available. Until patched, minimize exposure by restricting low-privilege user access to URL-related features.

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:< 2025.4.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
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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

  1. Confirm SolarWinds Observability Self-Hosted is installed
    Locate the installation directory, check the admin UI for product information, or query the system's running services for SolarWinds components
    Affected if The product is present on the system
  2. Determine the installed version
    Access the admin interface, check version information in the product's about or system settings, or inspect version files in the installation directory
    Affected if The installed version is lower than 2025.4.1 (e.g., 2025.4.0, 2025.3.x, or earlier)
  3. Identify if user-created URL fields exist in the environment
    Navigate to features where users can create or edit content containing URL parameters, such as dashboards, custom widgets, alerts, or notification configurations
    Affected if Users have access to input or edit URL-based fields in any part of the application
  4. Check for suspicious URL entries with embedded scripts
    Review stored URL configurations in the database or application configuration files, looking for URL values containing HTML tags, javascript: handlers, or event attributes like onload/onerror
    Affected if URL fields contain unsanitized script injections that could execute when rendered

You are affected if SolarWinds Observability Self-Hosted is installed with a version lower than 2025.4.1 and users have access to create or edit URL fields in any feature.

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

Implement context-aware output encoding and validation for URL fields, enforce Content Security Policy headers, and apply vendor-supplied patches when available. Until patched, minimize exposure by restricting low-privilege user access to URL-related features.

Recommended fix High confidence

2025.4.1 or later

  1. Review SolarWinds Observability Self-Hosted upgrade documentation at documentation.solarwinds.com
  2. Create a backup of your current installation and configuration
  3. Upgrade SolarWinds Observability Self-Hosted to version 2025.4.1 or later
  4. Verify the upgrade was successful and test that the XSS vulnerability is resolved in user-created URL fields

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
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26391 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-26391 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