New in CWP Edge-LatestFree with every CWPpro licenceWebsites up to 300x faster

CWP now includes LSPHP, LSAPI-Cache and CWP Cage at no extra cost with all CWPpro licences. The LSAPI-Cache plugin is integrated into our WordPress and other script installers, and CWP Cage gives every user complete isolation. Available now in the CWP Edge-Latest version.

Get CWPpro ›

Recent posts

#31
PHP / PHP Warns of Critical Security...
Last post by Starburst - November 19, 2026, 03:21:34 PM
The maintainers of the PHP programming language on Wednesday issued an advisory announcing an upcoming security release that addresses critical flaws.

The release is scheduled for November 19, 2026, between 2 and 2:30 p.m. UTC.

"These releases are part of PHP's regular four-week release cycle and will address security vulnerabilities affecting all supported PHP versions," the maintainers said. "The highest severity is CRITICAL."

However, the project also noted that issues rated critical require either non-default configuration or uncommon setups. It did not disclose any additional specifics.

The update is expected to include CVE-2026-115560, a remote code execution flaw that succeeds only if the following conditions are met -

An application sets session.serialize_handler to php_binary or php_serialize in its configuration, and its code switches the handler to php with ini_set() before calling session_start().
Session upload progress is enabled, which is PHP's default.
As mitigations, users were urged to set session.upload_progress.enabled=0 until the next regular bugfix release and restart the PHP worker for the setting to be applied.


Published Date: Nov 19, 2026

More Information:
https://thehackernews.com/2026/11/php-warns-of-critical-security-flaws.html
#32
Updates / Re: How to Switch Back from ED...
Last post by Starburst - November 19, 2026, 03:19:40 PM
Then you have to wait for LTS to catchup to the EDGE version.
#33
Updates / Re: How to Switch Back from ED...
Last post by rene_mix - November 19, 2026, 01:57:52 PM
Hi, the same thing happened to me; I was on the LTS version, and suddenly it appeared in the Edge version—it's working fine so far.
#34
Backup / Re: Back - restore email to ne...
Last post by Dangerousdave26 - November 19, 2026, 01:41:35 PM
Thank you.
#35
CentOS-WebPanel Bugs / Mailserver stats
Last post by anandmys - November 19, 2026, 11:42:23 AM
Mailserver stats not showing any data

Checked in 3 different VPS. All having same issue

AL8.10
CWPpro version: 2.0.18

#36
Updates / Re: How to Switch Back from ED...
Last post by Maz-V - November 19, 2026, 11:32:58 AM
Login to CWP Admin -> CWP Settings -> Edit Settings

This menu is located at the very top of the left sidebar.
#37
Updates / Re: How to Switch Back from ED...
Last post by anandmys - November 19, 2026, 11:31:48 AM
Any particular reason? Just curious
#38
Updates / How to Switch Back from EDGE t...
Last post by zeeky - November 19, 2026, 10:42:32 AM
Hi everyone, I was running the LTS version, but now it shows the EDGE version. How can I switch back to LTS?

I can't find an option in the panel.  :o
#39
CentOS-WebPanel Bugs / Re: CWP 1.30.24 – Default kern...
Last post by Wonder - November 19, 2026, 08:17:16 AM
Thanks for sharing the instructions!

I've already switched back to the stock AlmaLinux kernel using `grubby --set-default`, and everything is working fine after the reboot.

I also checked `/etc/cwpsecure/`. The `kernel_update.conf` file doesn't exist, but I found a `kernel_update.state` file containing `sk_ever_installed`.

For now, I'll leave the Secure Kernel packages installed and keep an eye on future CWP updates to see if the default kernel changes again.

Thanks again for your help!
#40
CentOS-WebPanel Bugs / Re: CWP 1.30.24 – Default kern...
Last post by 6Sense - November 19, 2026, 08:02:34 AM
CWP support gave me these instructions

1. stop CWP from re-pinning or reinstalling the Secure Kernel
mkdir -p /etc/cwpsecure
printf 'selfheal=0\nguard=0\nauto_install=0\n' >> /etc/cwpsecure/kernel_update.conf

2. list installed kernels and pick the newest stock one (without "cwpsec")
grubby --info=ALL | grep ^kernel

3. set it as default (replace with the exact path from step 2), check, then reboot
grubby --set-default /boot/vmlinuz-4.18.0-553.XX.X.el8_10.x86_64
grubby --default-kernel
reboot

After the reboot, "uname -r" should show the stock kernel. Optionally you can then remove the Secure Kernel packages: dnf remove 'kernel*cwpsec*'