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

SimpleHelp vulnerability

SimpleHelp contains an authentication bypass vulnerability in the OIDC authentication flow. When OIDC authentication is configured, identity tokens submitted during login are accepted without verifying their cryptographic signature. In a vu

Verdict

Today item — known-exploited.

Confirmed exploited in the wild (CISA KEV). Prioritize remediation now and verify exposure.

CISA KEV Yes · 2026-06-293EPSS 0.00721 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
3 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
blackpointcyber.com ↗kevintel.com ↗cisa.gov ↗Confirmed
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-06-29).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.00721 — 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-347 CWE-347 — weakness family: Cryptography.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-347 · CWE-347Cryptography
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board

Attacker/business narrative framing is pending triage for this record — see Coverage & confidence below. Facts and verdict above are derived deterministically from the public feed.

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)
  • EPSS probability (FIRST)
  • 3 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by VulnCheck (CNA)
  • Named finder/reporter credit (CVE.org)

    • 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.
  • Attacker/business narrative framing pending triage.
    • Disclosure & credit2
    Catalogued by VulnCheckCNA
    Credited with finding itZach Hanley (@hacks_zach) of Horizon3.aifinder