/

CVE-2026-72578

Severity:

HIGH RISK

(8.8)

Cross-Site Request Forgery (CWE-352) in FreePBX Framework 17

CVE-2026-72578

Deferred

Vulnerability type

Category:

Cross-Site Request Forgery

CWE:

CWE-352

Impact:

Unauthorized Administrative Actions

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A cross-site request forgery vulnerability in FreePBX Framework can allow an unauthenticated remote attacker to cause an authenticated administrator's browser to submit unwanted administrative requests. The risk arises when administrative actions accept cross-origin requests without sufficiently validating their origin or including an unpredictable request token.

Affected context

This issue affects FreePBX Framework deployments where administrative interfaces are reachable by an administrator's browser and sensitive state-changing requests do not consistently enforce CSRF protections. Exploitation generally depends on an administrator being authenticated and visiting attacker-controlled content while the administrative session remains active.

Exploit preconditions

  • Attack surface: Web-based FreePBX administrative interface
  • Required access: No direct FreePBX authentication is required by the attacker; an authenticated administrator must be targeted
  • Trigger point: A state-changing administrative request initiated through the administrator's browser
  • Why exploitation is possible: The application may accept a forged cross-origin request without sufficiently verifying a request-specific token, trusted origin, or equivalent browser-bound control

Why this happens

The vulnerability is caused by insufficient validation that a state-changing request originated from the legitimate FreePBX administrative interface. Under CWE-352: Cross-Site Request Forgery, the application relies on ambient browser credentials, such as session cookies, without requiring an additional unpredictable token or equivalent origin validation. As a result, a malicious site may cause a victim's browser to submit an administrative request using the victim's existing authenticated session.

Potential impact

  • An attacker may change administrative settings
  • An attacker could create, modify, or remove system resources permitted to the administrator
  • The application may be redirected toward insecure or malicious configurations
  • Administrative actions could cause service disruption or facilitate further compromise

General mitigation guidance

Mitigation generally focuses on ensuring that every state-changing administrative operation requires proof that the request originated from the trusted application.

Common defensive patterns include:

  • Applying unpredictable, session-bound CSRF tokens to state-changing requests
  • Validating trusted Origin or Referer values as a complementary control
  • Avoiding state changes through GET requests
  • Configuring session cookies with appropriate SameSite, Secure, and HttpOnly attributes
  • Reducing administrative privileges and separating high-impact operations where practical
  • Limiting exposure of administrative interfaces to trusted networks and users
  • Failing closed when CSRF tokens or origin checks are missing or invalid

How teams detect issues like this

Detection approaches can include:

  • Static analysis for state-changing routes that lack CSRF middleware or equivalent validation
  • Code review checks for administrative forms and API endpoints that rely only on browser cookies
  • Testing cross-origin requests against authenticated administrative workflows
  • Web application firewall or gateway policies that restrict unexpected origins for sensitive operations
  • Automated security testing that verifies invalid, missing, or cross-origin CSRF tokens are rejected
  • Monitoring administrative audit logs for unexpected changes associated with normal user browsing patterns

Sources

SourceLink
github.comgithub.com/FreePBX/framework
github.comgithub.com/FreePBX/framework/blob/release/17.0/amp_conf/htdocs/admin/libraries/BMO/Ajax.class.php

Frequently asked

questions

Yes, it may be remotely exploitable without direct authentication when an authenticated administrator can be induced to visit attacker-controlled content while their FreePBX session is active.

The attacker generally does not need to obtain the credentials. The targeted administrator's existing authenticated browser session supplies the credentials automatically when the forged request is accepted.

Require robust, session-bound CSRF tokens for all state-changing operations, supplemented by trusted-origin validation and secure cookie settings.

Apply CSRF protections consistently through centralized framework controls, prohibit state changes through GET requests, test administrative workflows for cross-origin behavior, and use least-privilege access controls.

Find out what's already
exploitable in your codebase.