dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 12 Mar 2026.
Web Help DeskApplication · Solarwinds

CVE-2025-26399

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-23
Fix available
A fix is available. Upgrade to after 12.8.6 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Zero-click Patch available

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 Web Help Desk was found to be susceptible to an unauthenticated AjaxProxy deserialization remote code execution vulnerability that, if exploited, would allow an attacker to run commands on the host machine. This vulnerability is a patch bypass of CVE-2024-28988, which in turn is a patch bypass of CVE-2024-28986.

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 · high confidence

SolarWinds Web Help Desk contains an unauthenticated deserialization vulnerability in the AjaxProxy component that allows remote code execution. This is a third iteration patch bypass (CVE-2024-28986 -> CVE-2024-28988 -> CVE-2025-26399), indicating the previous fixes did not fully address the underlying insecure deserialization issue.

MitigationApply the vendor patch immediately as this is an unauthenticated RCE with critical severity; until patched, consider network segmentation or disabling the AjaxProxy endpoint if possible.

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
Web Help DeskApplication
Affected:<= 12.8.6= 12.8.7

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Identify if SolarWinds Web Help Desk is installed
    Look for the SolarWinds Web Help Desk service or application on the system. Common installation paths include C:\Program Files\SolarWinds\Web Help Desk or /opt/solarwinds/webhelpdesk on Linux.
    Affected if The software is present on the system
  2. Check the installed version number
    Locate the version information for the installation, typically found in the application itself, an about page, or in installation metadata files. Compare your version against the affected ranges: versions 12.8.6 and below, or exactly version 12.8.7.
    Affected if The installed version is 12.8.6 or lower, or is exactly 12.8.7
  3. Verify the AjaxProxy component is accessible
    Check if the AjaxProxy endpoint is exposed. This is typically accessible at /helpdesk/AjaxProxy on the Web Help Desk server. Attempt to access this endpoint over HTTP/HTTPS to confirm it responds.
    Affected if The AjaxProxy endpoint responds and accepts requests without authentication
  4. Confirm the server is reachable over network
    Determine if the Web Help Desk interface is accessible from network locations, as this is an unauthenticated vulnerability. Check firewall rules and listening ports (default is port 8081 or 8443).
    Affected if The Web Help Desk service is reachable from network locations without authentication

If SolarWinds Web Help Desk is installed and the version is 12.8.6 or lower, or exactly 12.8.7, AND the AjaxProxy endpoint is accessible, the environment is affected by this unauthenticated RCE vulnerability.

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 a release after 12.8.6
Vendor patch www.solarwinds.com →
Interim mitigation

Apply the vendor patch immediately as this is an unauthenticated RCE with critical severity; until patched, consider network segmentation or disabling the AjaxProxy endpoint if possible.

Recommended fix Moderate confidence

Web Help Desk 12.8.8 or later

  1. Download Web Help Desk version 12.8.8 or later from the SolarWinds customer portal
  2. Back up the current Web Help Desk configuration and database
  3. Stop the Web Help Desk service
  4. Install the updated version following standard SolarWinds upgrade procedures
  5. Restart the Web Help Desk service
  6. Verify the AjaxProxy functionality is working correctly after the upgrade
  7. Monitor for any suspicious unauthorized access attempts
Caveat Review release notes for any configuration changes; standard upgrade should be straightforward

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

Fix this in Web Help Desk Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,560
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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