Security readout for executives and security teams
Plain-English summary
FreePBX systems before 17.0.8 can issue OAuth2 API tokens without confirming the correct client secret. An attacker still needs knowledge of a valid client_id, but successful abuse could give API access with high confidentiality and integrity impact.
Executive priority
Treat as a near-term remediation item for any internet-reachable or broadly accessible FreePBX deployment. The fix is identified, and the potential impact includes unauthorized API access affecting sensitive data and system state.
Technical view
The FreePBX api module OAuth2 flow did not sufficiently validate client credentials during token issuance. The source states ClientRepository.php validateClient() unconditionally returned true, allowing token issuance with a valid client_id and incorrect client_secret. Versions before 17.0.8 are affected; 17.0.8 fixes it.
Likely exposure
Exposure is likely limited to FreePBX deployments running the api module before 17.0.8, especially where API/OAuth2 endpoints are reachable by authenticated users or exposed networks.
Exploitation context
The provided sources do not report active exploitation, KEV listing, or public exploit availability. Abuse requires a valid client_id and the access conditions reflected by CVSS PR:L and AT:P.
Researcher notes
Evidence is strong for the root cause and fixed version, but limited on real-world exploitation. Focus validation on module version, OAuth client inventory, token issuance telemetry, and whether API endpoints are reachable beyond trusted administrators.
Mitigation direction
- Upgrade the FreePBX api module to 17.0.8 or later.
- Review vendor advisory guidance before applying compensating controls.
- Restrict access to FreePBX API/OAuth2 endpoints to trusted networks.
- Rotate OAuth2 client secrets after upgrading if exposure is suspected.
- Review API tokens and revoke unexpected or stale tokens.
Validation and detection
- Inventory FreePBX systems and confirm api module versions.
- Verify no affected deployment remains below 17.0.8.
- Review OAuth2 client records for unexpected client_id exposure.
- Check logs for unusual token issuance or API activity.
- Confirm endpoint exposure through firewall and access-control review.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-1390: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-44237 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.6 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
7.6HighVector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/FreePBX/security-reporting/security/advisories/GHSA-vgjf-4h63-8vccCVE reference, GitHub_M · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Weak Authentication
Weak Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.