basicsecurity.net
Proof, not just disclosure.
Threats / SimpleHelp / CVE-2024-57728
CVE-2024-57728 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-07

SimpleHelp vulnerability

SimpleHelp contains a path traversal vulnerability allowing authenticated administrators to upload arbitrary files via crafted zip archives, enabling remote code execution on the server.

Verdict

Today item, not a backlog item.

An authenticated admin can exploit zip slip to place malicious files anywhere on the filesystem and execute arbitrary code in the SimpleHelp server process context. Active exploitation and ransomware campaigns have been observed.

CISA KEV Yes · 2026-04-243Ransomware use Flagged3EPSS 0.5464 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-04-24), flagged for known ransomware use.
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.5464 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
FIRST EPSS ↗High
Severity / affected
Affected: SimpleHelp , SimpleHelp. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-22 Path Traversal — weakness family: Path traversal / file.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-22 · Path TraversalPath traversal / file
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No threat-actor attribution is established from the public feed 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 board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a zip file with path traversal sequences to escape the intended upload directory.
Business
Attacker gains ability to write files to arbitrary locations on the server.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I upload the malicious zip through the admin file upload function.
Business
Malicious payload is placed on the filesystem in a location where it will be executed.
3

Lateral reach — past segmentation narrative 3

Attacker
I trigger execution of the uploaded file to run arbitrary code as the SimpleHelp service user.
Business
Attacker achieves remote code execution with server privileges.
4

Data at risk — exfiltration narrative 4

Attacker
I use code execution to establish persistence and deploy ransomware or exfiltrate data.
Business
Systems are encrypted or data is stolen, causing operational disruption and financial loss.
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’t

Established (cited)

  • KEV listing (CISA)
  • Ransomware-use flag (CISA)
  • EPSS probability (FIRST)
  • CWE weakness mapping (NVD)
  • Catalogued by mitre (CNA)

    • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
    • Disclosure & credit2
    Catalogued by mitreCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.