CVE-2025-40552 — SolarWinds Web Help Desk Authentication Bypass (CVE-2025-40552)
SolarWinds Web Help Desk was found to be susceptible to an authentication bypass vulnerability that if exploited, would allow a malicious actor to execute actions and methods that should be protected by authentication.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Public exploit/PoC (nuclei)+4
- EPSS 52% (30-day exploitation probability)+15
- Technical severity (critical)+10
- CISA SSVC: exploitation "poc"+5
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Solarwinds Web Help Desk).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- EPSS ahead of 99% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Solarwinds | Web Help Desk | < 2026.1 | Vulnerable | NIST National Vulnerability Database |
| Solarwinds | Web Help Desk | version 12.8.8 HF1 and below | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.8 | CVSS 3.1 | Critical | 3.9 | 5.9 | psirt@solarwinds.com via NIST National Vulnerability Database |
| 9.8 | CVSS 3.1 | Critical | — | — | SolarWinds via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: psirt@solarwinds.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 52.00%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Analysis and videos
CVE-2025-40552: SolarWinds Web Help Desk Authentication Bypass
CVE-2025-40552 is a critical authentication bypass in SolarWinds Web Help Desk. According to the record, an attacker could reach actions and methods that should be protected by authentication. The CVSS 3.1 base score of 9.8 is attributed to the CNA, and the listed affected range is versions before 2026.1. The record does not show KEV listing, and no confirmed exploitation appears in the sources consulted.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · solarwinds/web help desk
- SSVC assessment updated
- Record published
- CVSS changed · 9.8
- Source status changed · → Modified
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
3 on the record
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-28299 SolarWinds Web Help Desk Denial-of-Service Vulnerability Jun 2, 2026
- Critical CVE-2025-40551 SolarWinds Web Help Desk Deserialization of Untrusted Data Vulnerability KEV Jan 28, 2026
- High CVE-2025-40537 SolarWinds Web Help Desk Hardcoded Credentials Vulnerability Jan 28, 2026
- Critical CVE-2025-40553 SolarWinds Web Help Desk: untrusted data deserialization leading to RCE Jan 28, 2026
- Critical CVE-2025-40554 SolarWinds Web Help Desk Authentication Bypass (CVE-2025-40554) Jan 28, 2026
- Critical CVE-2025-40536 SolarWinds Web Help Desk Security Control Bypass Vulnerability KEV Jan 28, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-40552 is "SolarWinds Web Help Desk Authentication Bypass (CVE-2025-40552)", rated Critical. It affects Web Help Desk (Solarwinds); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.8 describes technical severity. EPSS 52.00% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.