Submitted 18 hours ago by 
BlackEco@lemmy.blackeco.com to selfhosted@lemmy.world
Disclosure is scheduled at 14:00 UTC with attacks expected to follow soon after.
It is adviced to take offline every non-vital services until the patch has been installed (or the Docker image has been updated with a patched PHP)
I just happened to read this thread after deciding to open Jerboa after months and I stumbled into this, I have been updating my stuff for the past 30’, thank you for making this post and making me aware of this issue! (Even though I’m 8 hours late)
Nextcloud.
Spare a moment’s thought for the dev behind the ondrej PHP mirrors.
Could not pull shit from it this morning. I panicked because my distro’s repos did not have the version numbers of the patched packages, but apparently the Ubuntu maintainers back ported the patches. Sigh of relief.
Shouldn’t especially vital services be taken down to secure them?
Yep. Except if taking them down will kill people.
Natanox@discuss.tchncs.de 15 hours ago takes down 112 / 911 services
Don’t worry guys, we’re safe now! ꒰ঌ(˶ˆᗜˆ˵)໒꒱
Me when I take down only one hundred twelve out of nine hundred eleven services, leaving seven hundred ninety-nine services still running
As if those are running anything as recent as php.
It’s just one thing after another. I already had to make sure every computer and VPS has the updated CA certificates earlier today. Now I just finished disabling all of my web servers. I hope Debian doesn’t take forever getting the patch out.
Natanox@discuss.tchncs.de 15 hours ago They took just a few hours to squeeze out a new ca-certificates. On the other hand the last time there was a huge kernel bug it took well over 24 hours…
A bad ca is update a file on every pc and application. A kernal bug is way more involved so it doesn’t make a new problem later.
They took a lot longer than that on some past vulnerabilities, some of them sat unpatched for weeks or months. But it depends on the severity. A remote exploit of severity 9 will probably get expedited.
Why do it this way? I’m genuinely unaware.
With the plex2shell, they fixed it in a previous update, then told us later.
If PHP knows what the problem is, why announce it now, and then release the patch. Why not release the patch, say hey guys this is an important one, and then tell the world/every script kiddie who didn’t know about php2shell AFTER everyone is patched?
Like I get it, I guess, php2shell must already be happening, the vulnerability is already there, but like… Shut up about it? Right? Let more people patch before you announce why the patch exists?
I’m new to this world so maybe this is normal?
They originally tried to keep it secret but it got leaked. Initial reports were only that CVSS was 9.2 and it was a permissionless remote code execution exploit. After it got leaked what the exploit was, they gave up.
Plex is a closed source software, so it’s easier to just push an update and tell about this later. PHP is open source, so if they release a patch for it, you can immediately look up in the source code and find out what has been fixed and kind of reverse engineer what the problem could be.
As this is a very high-class vulnerability, I assume that it’s very easy to get into this so if you see the patch, it’s probably trivial to just find out what the issue is and immediately start attacking everyone. With this, at least most admins are ready and can plan in that on this time they should check into the issue and patch asap.
Ah that makes more sense, that’s the key I was missing, thank you
Using a tool like Shodan, I can quickly get a list of addresses that have a specific version of PHP behind it.
It sounds like this is a cvss 9.0 or higher for PHP which is bonkers because PHP is such a huge amount of the internet.
My guess is releasing these CVEs the normal way could have catastrophic consequences. They’re giving stsadmins a heads up so there is less of a scramble when sysadmins read “hey fix your shit it’s totally vulnerable” before they have their coffee.
Like as a sysadmin, this is a great way for them to do this.
I will in 10 mins alert my team that the whole site has to come offline for a period today. I don’t need to take it offline in an emergency and tell my boss to send out a memo.
I wonder how many docker containers keep their own version of PHP…
Services are only exposed on local WiFi and behind Tailscale, updated all as soon as possible: still quite safe right?
Yeah, as long as your firewall is properly hardened and up to date.
And not using php for a webui
The great hardening continues. Good to see.
The beatings cyberattacks will continue until morale security improves
laughs in keeping an old archive site still in PHP5
The vulnerabilities go back that far. You’re not safe.
Hey, never said I was laughing out of happiness… 😭
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| CA | (SSL) Certificate Authority |
| Plex | Brand of media server package |
| VPS | Virtual Private Server (opposed to shared hosting) |
[Thread #142 for this comm, first seen 21st Oct 2026, 12:40] [FAQ] [Full list] [Contact] [Source code]
Think of Louisiana before Katrina. Those systems of pumps and dykes are expensive and had been neglected… which was fine right up until they were severely tested by Katrina.
Our orange city counselman stopped funding repairs and inspections on the dykes and pumps many years ago. They’ve been deteriorating from neglect ever since.
A large hurricane is going to hit at 14:00 UTC
(In 10 minutes)
It’ll almost certainly be handled quietly and nobody will know but system admins, but this could be a bigger thing than usual.
Patches are showing up in the repos now. Ondrej and ubuntu 24.04 have them live now.
Synology had a critical system and PHP package update yesterday, could it be related 🤔
No, there is no fix released for this PHP vulnerability
Wouldn’t be surprised if the big guys got first dibs before everyone else
so for the docker images of PHP there currently seems to be no patch? or do you think the RC version includes the fix? Because it was released at 07:00UTC i would think it dosnt yet include the fix. dose anyone know how and where to check if the fix was applied? also do we know if docker hubs Vulnerabilities score already include php2shell CVEs?
fubarx@lemmy.world 13 hours ago
“I felt a great disturbance in the Force, as if millions of Wordpress sites suddenly cried out in terror and were suddenly silenced.”
hereiamagain@sh.itjust.works 12 hours ago
Seriously though, how quickly do you expect patches to be available for WordPress? I’ve got one WordPress site that I made years ago for a friend’s business. I pop in on it and update stuff every few months.
Should I take it down?
GreenKnight23@lemmy.world 2 hours ago
depends. do you want to deal with a simple patch in 24 hours or do you want to rebuild an entire legacy system from nothing (assuming you don’t take proper backups).
MouldyCat@feddit.uk 11 hours ago
it’s PHP that needs the patches. Yes you should take the site down until PHP has been patched.
it’s a lot more than wordpress…