All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
aaPanel Update Announcement
aaPanel_team
Member, Patron Provider
aaPanel Beta 8.26.0 Update Announcement
1. Added: One-click temporary hardening for PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619 in Home - Security (please upgrade PHP to the patched version)
2. Added: Disk usage statistics by category in Home
3. Added: Custom site renaming and copying of site names in Website - PHP Project
4. Added: Scan & Import now supports PM2 projects in Website - Node.js Project
5. Added: Support creating Go projects by scanning processes in Website - Go Project
6. Added: Custom names supported when adding/modifying tasks in Cron
7. Optimized: Pro version/plugin purchase and license usage pages
8. Optimized: Resolved the cross-site issue in multi-service WP Toolkit; added SNI-related configuration for SSL deployment
9. Fixed: Requests for bound domains did not display data in Node.js Project
10. Fixed: An issue where a crash in the Opcache.jit process prevented adding WordPress sites
11. Updated: Nginx WAF plugin now supports blocking the PHP php2shell vulnerability
Comments
Is it necessary for us to fix PHP 5.4–5.6?
Probably best just to include a calendar in the control panel so users can see what year it is.
Are you trying to show them just how old PHP 5.4 is, so that they’ll opt for a newer version of PHP?
Is it really a question to even provide 5.4
Just making a joke about the age of PHP 5.4
I think there might be a misunderstanding. Although this version is quite old, some users still reach out to us requesting patches for PHP 5.6; I’m simply trying to gauge how many users are still running this version of PHP.
in era of PHP 8.5 and soon PHP 9 coming, who on the earth still using PHP 5?
They still use it?
You might find this quite surprising, but let’s try to be a bit more understanding.
Yes, but only a very small number.
I have a question , why
Same reason there are critical servers in production today running the 2.4 kernel.
It may be that some legacy systems have been running for a long time, and upgrading them would only cause more trouble.
No, not upgrading them is what causes more trouble.
I know that upgrading old systems can be a real pain and expensive as fuck, but not upgrading them will eventually turn out to be an even bigger pain and even more expensive.
Yes.
Please also put back the Microsoft Access database extension for Personal Homepage Preprocessor, as well as OLE object support so that we can load Excel from the web server running in Administrator privilege.
Is it humor?
Yes, migrating the system is quite a hassle—but compared to the trouble it could cause later on, it’s really no trouble at all.
I agree. Some people still use php 5.6
@aaPanel_team will be great if you include an updated version for php 5.6
PHP 5.4 to 5.4.46:
PHP 5.5 to 5.5.39:
PHP 5.6 to 5.6.41 (aaPanel AI patched build):
This version is released for testing and has not yet undergone validation in a live production environment.
Please verify it in a testing environment first; we do not recommend using it directly in production without prior validation. Before updating, ensure you back up your site, database, PHP environment, and configurations, or create a server snapshot. The update process will restart the relevant PHP services. Should any issues arise—such as problems with extensions or the website itself—please use your backups to restore the system promptly.
What, no patches for PHP/FI?
You’re too kind! When users share their needs or feedback with us, it’s only natural that we do our best to resolve their issues.
This is way too old...
8.27.0Beta Version Release Notes
Holy crap, I thought my memory of Microsoft FrontPage Server Extensions (FPSE) had been flushed long ago, but this made me flash back to it.
There was a time when customers would specifically request a hosting provider to install FPSE and would shop web hosts based on whether or not it was available. Web hosts would advertise that they supported it.
I just looked and Microsoft dropped Unix support in 2006.
But I mean, hey, if you're going to support PHP 5.4...you should include FPSE support as well.