Widespread PHP Flaw

They are affected but I would hope you don't have your web interfaces exposed to the internet . . . like yikes.

Almost every website in the world has web interfaces exposed to the internet, non ?

This website does (Xenforo), Wordpress does. 70% of all websites in the world are php.
 
For those using older distros which are EOL there are couple of which can be done:

Recompile PHP with this patch:


The PHP project lists configuration measures that reduce exposure but, in their own words, do not make the installation safe. Treat this as a temporary step until you can update PHP, not as a fix:


  • session.upload_progress.enabled = 0
  • memory_limit = -1 (set so it cannot be overridden per application; see the caution below)
  • post_max_size kept low (see the ASTPP note below)
  • upload_max_filesize kept below post_max_size

Apply these in php.ini or your FPM pool configuration, not with ini_set() or .user.ini, and restart every PHP worker afterwards.


Two cautions specific to ASTPP, please read before applying:


  • ASTPP uses file uploads for rate card and DID imports. If you set post_max_size too low, large imports will fail. The PHP advisory suggests 32M where uploads are needed. Set it based on your largest import, and test an import after applying.
  • memory_limit = -1 removes the PHP memory ceiling. This is the PHP-recommended mitigation, but it means a single request is no longer capped, which is an availability consideration on a production server. If you can, use an operating-system level limit (container or cgroup) as the safety boundary instead, and do not use RLIMIT_AS or RLIMIT_DATA.

Always back up your existing php.ini before changing it.
 
Almost every website in the world has web interfaces exposed to the internet, non ?

This website does (Xenforo), Wordpress does. 70% of all websites in the world are php.

Yes, but your Freepbx based ones should never be exposed to the internet at large. Ever. Its' just not secure enough.
 
Yes, but your Freepbx based ones should never be exposed to the internet at large. Ever. Its' just not secure enough.
3cx required me to have a split DNS, is there any security risk in that ?
 
That's why a whitelist only IncrediblePBX stock install is really not affected by this.
That is definitely something worth bragging about. I think PIAF was very security focused and that tradition has carried on.

Not inherently, no, split DNS just basically means public and private resolve to different IP's.
So, IncrediblePBX doesn't need that because ... ? Why does 3CX essentially force it on people ? Security ? Protect their licenses ?
 
Oct 20, 2026 4:27 PM

a quick demo of php2shell on all major website hosting software packages and how quick it is ....

I heard having cloudflare helped.
 
Last edited:

Latest Posts

Forum statistics

Threads
26,841
Messages
175,462
Members
20,384
Latest member
ezoNet
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Back
Top