PHP2Shell statement record · Platform

FreePBX and PHP2Shell

FreePBX's PHP2Shell statement is recorded as customer must update, with statement date printed as October 23, 2026, 4:53pm (as printed); read the published statement.

This index reports published statements and AI answers on stated dates. It is not a security assessment. For patching, follow PHP's advisory and your host.

Last checked . Last refreshed .

Submit a correction or your statement Get the badge All statements

Is this your company?

Publish or update your statement. The statement submission is free.

See what ChatGPT, Claude, Perplexity, Google AI Overviews and Google AI Mode say about you: the $490 PHP2Shell Record Check.

We capture the dated answers, trace wrong or missing statements to their sources and deliver a statement page in the format the engines quote.

Agencies: white-label PHP2Shell Record Check, $490 per client report.

The record

Company
FreePBX
Domain
freepbx.org
Group
Platform
Index category
not an Index vendor
Status
customer must update
Statement found
yes
Statement
https://community.freepbx.org/t/critical-php-security-vulnerabilities-action-required-for-freepbx-and-pbxact/110423
Statement date
October 23, 2026, 4:53pm (as printed)
Fixed version named
no
Worker restart stated
no
End of life plan stated
yes
Source type
official team forum notice
Places checked
Last checked

The statement

Apply the latest PHP security updates by following the standard system software update procedures outlined in our documentation.

Read the statement on community.freepbx.org, dated October 23, 2026, 4:53pm (as printed). Source type: official team forum notice.

Notes

Apply the latest PHP security updates by following the standard system software update procedures outlined in our documentation. Notice posted by penguinpbx (C. Maj), signed Sangoma Open Source Team on the official FreePBX forum. Version 17 users must apply standard PHP security updates. Version 16 and earlier users are asked to migrate to version 17; patched PHP 7.4 is offered for testing, not stated as a completed production rollout.

Change log

What the five engines said

AI answers not yet measured

Submit a correction or your statement

Submit a correction or your statement. We list a statement only once we have opened it on your own domain or verified official account. Disputes follow the dispute policy. Or email the statement link to index@broadcastwell.com.

Badge

The badge for FreePBX reads PHP2Shell statement listed, Verified 24 October 2026, Broadcastwell, and links to this record. Badge and embed code · Badge terms.

Questions about FreePBX and PHP2Shell

Is FreePBX affected by PHP2Shell?

FreePBX's PHP2Shell statement is recorded as customer must update, with statement date printed as October 23, 2026, 4:53pm (as printed); source: https://community.freepbx.org/t/critical-php-security-vulnerabilities-action-required-for-freepbx-and-pbxact/110423.

The status records what the company published, under our statement status rules. A PHP version mentioned in a statement can be guidance for other organisations; the statement and notes explain its scope.

About this page

This index reports published statements and AI answers on stated dates. It is not a security assessment. For patching, follow PHP's advisory and your host.

Last refreshed .

PHP2Shell Statement Index · AI Answer Watch · Download the data · Submit a statement · Dispute policy