Threats / SimpleHelp / CVE-2024-57726
CVE-2024-57726
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
SimpleHelp vulnerability
SimpleHelp contains a missing authorization vulnerability allowing low-privileged technicians to create API keys with excessive permissions, enabling privilege escalation to server admin role.
Verdict
Today item, not a backlog item.
Low-privileged technicians can bypass authorization controls to generate API keys with unrestricted permissions, achieving administrative access and full system compromise. Active exploitation and ransomware deployment observed.
CISA KEV Yes · 2026-04-244Ransomware use Flagged4EPSS 0.08632 (verify live)5CVSS 9.9 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
21 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-04-24), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.08632 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.9 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) · Affected: SimpleHelp , SimpleHelp. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-862 Missing Authorization — weakness family: Authorization / access control.CWE assignment from the public NVD record (may be stale); 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 464 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.
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 authenticate as a low-privileged technician account within SimpleHelp.
Business
Legitimate support staff credentials are compromised or misused, creating insider threat exposure.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I create API keys through the application without proper authorization checks validating my permission level.
Business
Access control enforcement fails, allowing unauthorized credential generation at any privilege tier.
3
Lateral reach — past segmentation narrative 3
Attacker
I assign excessive permissions to the generated API keys, including server admin role capabilities.
Business
Permission boundaries collapse, granting full administrative control through programmatic access.
4
Data at risk — exfiltration narrative 4
Attacker
I use the admin-level API keys to assume server administrator role and control the entire SimpleHelp infrastructure.
Business
Complete system compromise enables data exfiltration, service disruption, and lateral movement to connected systems.
5
Lights out — disruption & extortion narrative 5
Attacker
I deploy ransomware or maintain persistent access across the compromised environment.
Business
Operations halt, customer data is encrypted or stolen, and recovery costs escalate with ransom demands.
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