On Wednesday, October 21, 2026, the web went into a frenzy. A major PHP vulnerability had just been disclosed, and its severity sent pressure soaring around the globe: major government websites were temporarily taken offline, and the story made the evening news on the big TV networks! PHP has rarely been in the spotlight like this. It wasn’t exactly good press, but it sure highlighted how ubiquitous PHP is... whatever its critics may say 😉

What does this have to do with Piwigo? Piwigo is written in PHP, which means PHP has to run on your servers for Piwigo to work. Piwigo itself isn’t directly affected by the vulnerability, but since some users install PHP only to run Piwigo, we decided to tell you about it.
To put it simply: the vulnerability lets an attacker run any code they want on the server. That makes it potentially very serious. You need to update your servers to the latest PHP releases, which are patched against this vulnerability:
- PHP 8.2 => 8.2.35
- PHP 8.3 => 8.3.36
- PHP 8.4 => 8.4.27
- PHP 8.5 => 8.5.12
Note that older versions have no fix. If you’re still running PHP 7 (or even PHP 5), it’s time to stop procrastinating and move to PHP 8.2 or later. The latest Piwigo release, 16.4.0, runs smoothly on all the PHP versions patched for this vulnerability.
⚠️ Updating Piwigo without updating PHP does not protect you at all. You need to update PHP.
There are several ways to host your Piwigo:
- Piwigo Self-Hosted on shared hosting: your hosting provider should already have taken care of it. Still, double-check in your Piwigo, on the [Administration > Tools > Maintenance > Environment tab] page, that your PHP version is one of those listed above.
- Piwigo Self-Hosted on a server you manage: the update is up to you. Use your distribution’s package manager. On Debian, which is what we use at Piwigo, apt update && apt upgrade does the job. You do need to be on a recent release of your distribution, though (the latest one, or at worst the previous one). On Debian, for example, the updates were only made available for Debian 12 and 13.
- Piwigo Self-Hosted installed from the official Docker image: apply the update offered in your Piwigo, on the [Administration > Tools > Updates] page. You need at least version 16.4.0c.
- Piwigo Cloud: we’ve already taken care of everything.
On our end, we run dozens of servers for piwigo.org and Piwigo Cloud. Even though we kept calm, the widespread panic still had an impact on us. Several users and customers reached out to ask how much Piwigo was affected, hence this announcement. We also had to upgrade several servers that were still running PHP 5.6 or 7. That often means rewriting PHP code, or even switching to different applications altogether. For example, we’ve moved to a brand-new forum, and the translation platform is still a work in progress... Long story short, the past few days have been pretty hectic!
On Piwigo Cloud, we monitor web traffic, and we can confirm that “vulnerability scanners” are out there: bots that automatically crawl the web to build lists of sites affected by the vulnerability. So the threat and the risk are very real. That said, we haven’t seen any successful attack on our servers, but we’re staying on our toes!