CVE-2025-40536: SolarWinds Web Help Desk Security Control Bypass Vulnerability
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
SolarWinds Web Help Desk was found to be susceptible to a security control bypass vulnerability that if exploited, could allow an unauthenticated attacker to gain access to certain restricted functionality.
Description quoted from the CVE record (assigned by SolarWinds, published 2026-01-28).
Weakness: CWE-693 Protection Mechanism Failure
How it can be exploited
Exploitable over the network with high attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: no. Technical impact: total.
- On CISA KEV since
- 2026-02-12
- US federal deadline
- 2026-02-15
- Ransomware use
- Not known
Public exploit evidence (Exploit Observer)
Also known as: BDU:2026-00930, CNNVD-202601-4806, EUVD-2025-206418, GHSA-m83h-48rr-jcrh
VEDAS cluster: VEDAS:DRAKEDESTROYER
Exploit Observer links 7 pieces of public exploit code or detection modules that name this CVE or one of its aliases.
Exploit code and modules (7)
Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.
- Nuclei template: https://raw.githubusercontent.com/projectdiscovery/nuclei-templates/main/http/cves/2025/CVE-2025-40536.yaml
- Code repository: https://github.com/victoriaalicex/cve-2025-40536-analysis
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/nuclei/2025/CVE-2025-40536.yaml
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/nuclei/2025/CVE-2025-40536.yaml
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2025/CVE-2025-40536.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2025/CVE-2025-40536.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2025/CVE-2025-40536.rules
Vulnerability databases and vendor advisories (8)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://euvd.enisa.europa.eu/enisa/EUVD-2025-206418
- Vulnerability database or vendor advisory: https://github.com/advisories/GHSA-m83h-48rr-jcrh
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2025-40536
- Vulnerability database or vendor advisory: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-40536
- Vulnerability database or vendor advisory: https://www.cnnvd.org.cn/home/globalSearch?keyword=CNNVD-202601-4806
- Vulnerability database or vendor advisory: https://www.solarwinds.com/trust-center/security-advisories/CVE-2025-40536
- Vulnerability database or vendor advisory: https://www.solarwinds.com/trust-center/security-advisories/cve-2025-40536
- Vulnerability database or vendor advisory: https://www.tenable.com/cve/CVE-2025-40536
23 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 0.736
very likely to be attacked soon - VEDAS
- 0.989
strong exploit evidence - On CISA KEV
- Yes, since 2026-02-12
Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish. The vertical line is the day CISA added it to its exploited list.
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| SolarWinds Web Help Desk | version 12.8.8 HF1 and below | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
Exploit Observer also maps it to: solarwinds web_help_desk, solarwinds_inc. solarwinds_web_help_desk.
How to fix it
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Vendor guidance:
- https://www.solarwinds.com/trust-center/security-advisories/CVE-2025-40536 (vendor-advisory, patch)
- https://documentation.solarwinds.com/en/success_center/whd/content/release_notes/whd_2026-1_release_notes.htm (release-notes)
How to detect it
Nuclei template (active check)
SolarWinds Web Help Desk - Vulnerability
SolarWinds Web Help Desk was found to be susceptible to a security control bypass vulnerability that if exploited, could allow an unauthenticated attacker to gain access to certain restricted functionality.
Name and description quoted from the template, written by VEDAS.
The template sends 1 request (GET /helpdesk/WebObjects/Helpdesk.woa); it decides using dsl, regex, word matchers. Severity in the template: high. Marked as not yet verified against a live vulnerable target.
Run it against a host you own or are authorised to test:
nuclei -u https://your-host -t CVE-2025-40536.yamlShow the template (54 lines)
id: CVE-2025-40536
info:
name: "SolarWinds Web Help Desk - Vulnerability"
author: vedas-arpsyndicate
severity: high
description: |
SolarWinds Web Help Desk was found to be susceptible to a security control bypass vulnerability that if
exploited, could allow an unauthenticated attacker to gain access to certain restricted functionality.
reference:
- https://www.exploit.observer/?keyword=CVE-2025-40536&match=exact
- https://subdomain.center/?engine=ammonites&keyword=solarwinds&match=exact
classification:
cvss-metrics: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
cvss-score: 8.1
cve-id: CVE-2025-40536
cwe-id: CWE-693
metadata:
verified: false
tags: cve,cve2025,solarwinds,webhelpdesk,kev,vkev,passive
http:
- method: GET
path:
- "{{BaseURL}}/helpdesk/WebObjects/Helpdesk.woa"
host-redirects: true
max-redirects: 2
extractors:
- type: regex
name: build_token
part: body
group: 1
regex:
- "\\?v=([0-9]+_[0-9]+_[0-9]+_[0-9]+)"
internal: true
- type: dsl
name: version
dsl:
- "replace(build_token, '_', '.')"
matchers-condition: and
matchers:
- type: word
words:
- "Web Help Desk Software"
- "SolarWinds WorldWide"
- "/WebObjects/Helpdesk.woa"
condition: or
- type: dsl
dsl:
- "compare_versions(version, '< 12.8.8.2585')"
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2025-40536 SolarWinds Web Help Desk - Vulnerability. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2025-40536 SolarWinds Web Help Desk - Vulnerability"; flow:established,to_server; http.uri; content:"/helpdesk/WebObjects/Helpdesk.woa"; nocase; fast_pattern; classtype:web-application-attack; reference:cve,CVE-2025-40536; reference:url,https://www.exploit.observer/?keyword=CVE-2025-40536&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=solarwinds&match=exact; sid:1009000; rev:1;)
CVE-2025-40536.rules on GitHub
References
Vendor advisories and patches
- https://www.solarwinds.com/trust-center/security-advisories/CVE-2025-40536 (vendor-advisory, patch)
- https://documentation.solarwinds.com/en/success_center/whd/content/release_notes/whd_2026-1_release_notes.htm (release-notes)
Exploits and technical analysis
- https://www.huntress.com/blog/active-exploitation-solarwinds-web-help-desk-cve-2025-26399 (third-party-advisory)
Government sources
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-40536 (government-resource)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.