basicsecurity.net
Proof, not just disclosure.
Threats / Sangoma / CVE-2025-57819
CVE-2025-57819 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Sangoma FreePBX vulnerability

Sangoma FreePBX contains an authentication bypass vulnerability allowing unauthenticated access to the administrator interface, enabling arbitrary database manipulation and remote code execution.

Verdict

Today item — known-exploited.

An unauthenticated attacker can bypass authentication due to insufficient input sanitization, gain administrative access to FreePBX, manipulate the database, and execute arbitrary code on the system. This vulnerability is actively exploited in the wild.

CISA KEV Yes · 2025-08-293EPSS 0.8736 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
161 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 2025-08-29).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.8736 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Sangoma, FreePBX. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-89 SQL Injection, CWE-288 Auth Bypass via Alternate Path — weakness family: Injection, Authentication.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
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
1

Front door — unauthenticated access narrative 1

Attacker
I craft a request that bypasses the authentication mechanism by exploiting insufficient input sanitization in FreePBX.
Business
The organization loses control of access to its communications infrastructure as authentication controls fail to protect the administrator interface.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I gain unauthenticated access to the FreePBX administrator panel without valid credentials.
Business
Administrative privileges are compromised, exposing the entire system to unauthorized modification and control.
3

Lateral reach — past segmentation narrative 3

Attacker
I manipulate the FreePBX database directly through the compromised administrator interface to alter configurations and user data.
Business
Data integrity is compromised, affecting call routing, user accounts, billing records, and system configuration.
4

Data at risk — exfiltration narrative 4

Attacker
I execute arbitrary code on the FreePBX server through the administrative access I obtained.
Business
The organization's communications system is fully compromised, potentially affecting all dependent business operations and exposing sensitive call data.
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)
  • Weaponized exploit available (VulnCheck)
  • 161 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by GitHub_M (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 GitHub_MCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.