Threats / SolarWinds / CVE-2025-40536
CVE-2025-40536
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
SolarWinds Web Help Desk vulnerability
SolarWinds Web Help Desk contains a security control bypass vulnerability allowing unauthenticated attackers to access restricted functionality.
Verdict
Today item — known-exploited.
An unauthenticated attacker can bypass security controls in Web Help Desk to reach functionality intended for authorized users. Active exploitation in the wild increases urgency for patching.
CISA KEV Yes · 2026-02-125EPSS 0.71545 (verify live)6CVSS 8.13CISA SSVC Exploitation: active · Automatable: no · Impact: total4Exploit Weaponized · public exploit · Metasploit module · nuclei template14
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-02-12).
Probability (EPSS)
EPSS 0.71545 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.1 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: SolarWinds, Web Help Desk. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-693 Protection Mechanism Failure.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 15 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify that Web Help Desk exposes restricted functionality without proper authentication enforcement.
Business
Unauthorized access to help desk systems compromises confidentiality of support tickets, customer data, and internal communications.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the control bypass to access administrative or sensitive operational features without credentials.
Business
Attackers gain ability to modify support workflows, escalate privileges, or pivot to connected systems and data repositories.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage unrestricted access to extract sensitive information or establish persistence within the help desk infrastructure.
Business
Incident response and forensic capabilities are undermined; attackers may maintain long-term access to organizational support operations.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by SolarWindsCNA
Credited with finding itJimi Sebree working with Horizon3.aifinder