PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-72578 FreePBX CVE debrief

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-10T11:17:30.660Z and has not been modified since then. The vulnerability is a cross-site request forgery (CSRF) in FreePBX Framework 17.0, allowing an unauthenticated remote attacker to perform administrative actions on behalf of an authenticated administrator. This CSRF vulnerability has a CVSS score of 8.8 and is classified as HIGH severity. Administrators and users of FreePBX Framework 17.0 should prioritize patching to prevent potential administrative actions by unauthenticated remote attackers. The affected product is FreePBX Framework 17.0. Defenders should prioritize patching to prevent potential administrative actions by unauthenticated remote attackers. Further verification of affected systems and vendor remediation is needed.

Vendor
FreePBX
Product
FreePBX Framework
CVSS
HIGH 8.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-10
Original CVE updated
2026-08-28
Advisory published
2026-08-10
Advisory updated
2026-08-28

Who should care

Administrators and users of FreePBX Framework 17.0, as well as security teams responsible for monitoring and patching vulnerabilities, should prioritize patching to prevent potential administrative actions by unauthenticated remote attackers. Operators of affected systems should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Technical summary

A cross-site request forgery (CSRF) vulnerability in FreePBX Framework 17.0 allows an unauthenticated remote attacker to perform administrative actions on behalf of an authenticated administrator. The vulnerability has a CVSS score of 8.8 and is classified as HIGH severity. The affected product is FreePBX Framework 17.0. Defenders should prioritize patching to prevent potential administrative actions by unauthenticated remote attackers.

Defensive priority

Administrators of FreePBX Framework 17.0 should prioritize patching to prevent potential administrative actions by unauthenticated remote attackers.

Recommended defensive actions

  • Patch FreePBX Framework 17.0 to prevent CSRF attacks
  • Verify and apply vendor remediation
  • Monitor for suspicious administrative actions
  • Inventory and check systems for potential exposure
  • Review compensating controls for exposed systems
  • Check relevant monitoring, detection, and logs for exposed assets
  • Track exceptions and retest remediated assets

Evidence notes

The CVE record and NVD detail provide information on the CSRF vulnerability in FreePBX Framework 17.0. Further verification of affected systems and vendor remediation is needed. The vulnerability has a CVSS score of 8.8 and is classified as HIGH severity. Administrators should verify the affected scope and apply vendor remediation. Monitoring for suspicious administrative actions is recommended.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-72578 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-72578

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-72578 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-72578

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://github.com/FreePBX/framework

    309f9ea4-e3e9-4c6c-b79d-e8eb01244f2c

  • Source reference

    Unverified legacy reference

    URL: https://github.com/FreePBX/framework/blob/release/17.0/amp_conf/htdocs/admin/libraries/BMO/Ajax.class.php

    309f9ea4-e3e9-4c6c-b79d-e8eb01244f2c

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.