How severe is GHSA-m42g-xg4c-5f3h?

No CVSS score has been assigned to GHSA-m42g-xg4c-5f3h yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m42g-xg4c-5f3h?

Affected package information for GHSA-m42g-xg4c-5f3h is not yet fully mapped. Check the official advisory links for details.

How do I fix GHSA-m42g-xg4c-5f3h?

Upgrade the affected component to the fixed release for GHSA-m42g-xg4c-5f3h, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.

How do I detect GHSA-m42g-xg4c-5f3h in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate GHSA-m42g-xg4c-5f3h if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is GHSA-m42g-xg4c-5f3h actively exploited in the wild?

Yes. There are 8 known exploit references for GHSA-m42g-xg4c-5f3h, including 1 documented proof-of-concept exploit on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-m42g-xg4c-5f3h?

GHSA-m42g-xg4c-5f3h has an EPSS (Exploit Prediction Scoring System) score of 95.0%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is GHSA-m42g-xg4c-5f3h in the CISA Known Exploited Vulnerabilities catalog?

Yes. GHSA-m42g-xg4c-5f3h (Sangoma FreePBX Authentication Bypass Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-08-29. CISA required all US federal civilian agencies to remediate this vulnerability by 2025-09-19. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is GHSA-m42g-xg4c-5f3h?

GHSA-m42g-xg4c-5f3h is classified as SQL Injection (CWE-89), CWE-288 (CWE-288). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for GHSA-m42g-xg4c-5f3h?

A Nuclei detection template exists for GHSA-m42g-xg4c-5f3h, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-m42g-xg4c-5f3h published, and has it been updated?

GHSA-m42g-xg4c-5f3h was published on August 28, 2025 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV · ACTIVELY EXPLOITED

FreePBX Affected by Authentication Bypass Leading to SQL Injection and RCEGHSA-m42g-xg4c-5f3h

GHSA-m42g-xg4c-5f3h is a SQL Injection vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2025-08-29) — treat it as actively exploited and patch now. A fix is available — see the affected versions and patch details below.

Published

Aug 28, 2025

Updated

Oct 24, 2026

Affected

1 product

Patched

See advisory

Exploits

8 known

Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2025-08-29. Federal agencies were required to remediate by 2025-09-19.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for GHSA-m42g-xg4c-5f3h.

EPSS Exploitation Probability

via FIRST.org ↗

95.0%probability of exploitation in next 30 days

Very High Risk+9.56%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

FreePBX is an open-source web-based graphical user interface. FreePBX 15, 16, and 17 endpoints are vulnerable due to insufficiently sanitized user-supplied data allowing unauthenticated access to FreePBX Administrator leading to arbitrary database manipulation and remote code execution. This issue has been patched in endpoint versions 15.0.66, 16.0.89, and 17.0.3.

Affected Products

1 product · 3 configurations

Application

freepbxsangoma

≥ 17.0 && < 17.0.3

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52681webappsmultiple

FreePBX 17.0.2 - Remote Code Execution (RCE)

by Jared Brits · Sep 3, 2026

Exploit-DB Source

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Fix
Upgrade the affected component to the fixed release for GHSA-m42g-xg4c-5f3h, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

How to detect GHSA-m42g-xg4c-5f3h

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id ghsa-m42g-xg4c-5f3h -u https://target

Template: FreePBX - Remote Code Execution
Severity: critical
Impact: Unauthenticated attackers can manipulate database records through SQL injection and achieve remote code execution through file upload path traversal, achieving complete system compromise.
Remediation: Upgrade FreePBX to version 15, 16, or 17 with the latest security patches and lock down administrator access as described in the FreePBX security advisory.

Template by ProjectDiscovery nuclei-templates (watchtowr, pussycat0x, DhiyaneshDk), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-m42g-xg4c-5f3h in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works