"I felt a great disturbance in the Force, as if millions of Wordpress sites suddenly cried out in terror and were suddenly silenced."
post
Shouldn't especially vital services be taken down to secure them?
takes down 112 / 911 services
Don't worry guys, we're safe now! ꒰ঌ(˶ˆᗜˆ˵)໒꒱
As if those are running anything as recent as php.
Safe here, we use 999
round these parts we use 0118 999 881 999 119 725 3
Me when I take down only one hundred twelve out of nine hundred eleven services, leaving seven hundred ninety-nine services still running
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.
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 I think…
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?
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...
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.
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.
They didn't move fast enough on it and others began circulating it. So they had to play catch up, hence the need to react before they had a patch.
We won't pretend otherwise: the delay was a structural failure, caused by both the security team's decision process and its lack of resources. The security team has since started changing its processes, and that work continues, so that decisions can be made by majority and compromises are encouraged.
Wow, this article really reads as LLM-generated to me. The quoted section with the "We won't pretend otherwise:", the second paragraph in:
This post isn't about how to update. It's about how these vulnerabilities were found and fixed, what has changed in how PHP security is handled over the past two years, and what we need from the organizations that depend on PHP to keep PHP's security work going.
Could they not be bothered to write a write-up about such a critical severity?
Spare a moment's thought for the dev behind the ondrej PHP mirrors.
Services are only exposed on local WiFi and behind Tailscale, updated all as soon as possible: still quite safe right?
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 (when he destroyed CISA). 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.
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
Dibs on the patches? They are not finite.
laughs in keeping an old archive site still in PHP5
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)
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) |
3 acronyms in this thread; the most compressed thread commented on today has 19 acronyms.
[Thread #142 for this comm, first seen 21st Oct 2026, 12:40] [FAQ] [Full list] [Contact] [Source code]
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. edit: nvm the patched versions without RC are now also in the docker hub repos.
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?
Patches are showing up in the repos now. Ondrej and ubuntu 24.04 have them live now.
https://github.com/syhunt/php2shell-protection
has some background and possible mitigations. But I shut down all my php sites...
It's wild to me that people are still using PHP in 2026. It was known to be a god awful trainwreck of a language all the way back in like 2005 and it certainly hasn't improved much since then. I guess that's what happens when a language peaks right at the height of the dotcom bubble.
Symphony / Laravel is still super popular. I was gonna apply to a job posting at my partner's company, but I went "eh nvm" when I saw they were using Symphony 😭
I used it quite a bit right at the beginning, when it was transitioning from being a "Pre-HTML Processor" templating utility to a proper language.
The syntax was nice and easy to pick up. The rest was pretty bad, a lot of security was left to the developer following best practices.
It improved with time, but it had already left a bad impression on me.
I know it's still popular, as you can tell from the downvotes.
You have no idea what you're talking about.
I've been a professional programmer for over 30 years with some of the biggest companies in the world. I've worked with assembly, c, c++, c#, java, kotlin, perl, lua, haskell, rust, javascript, typescript, coffeescrpit, dart, php, python, and I'm sure 3 or 4 other languages I've just forgotten about at this point. Some of those languages are terrible and I hope never to touch again, others were great and I'd be happy to work with.
PHP should have been retired as a language 20 yeara ago, but WordPress has kept it alive all this time. The rest of the industry has moved on and learned lessons from what came before, but the sheer momentum of hundreds of thousands of WordPress installs has somehow kept PHP alive. The language started as a hack, and it remains a hack. It's gotten faster over the years, but it's still just as badly designed today as it was when it was originally created.
As a security auditor, I would have specified that it's the OLD php plugins/scripts extensibility that was the mess. And similar to CGI, PHP used to be a problem for infosec audits because it was usually so full of configuration holes that the mantra just became "Don't use PHP". AJAX implementations are also rife with security issues because of configuration errors. So is a default implementation of nginx.
But PHP gets the bad rep because it was hands down the most popular way to add custom functionality to a webapp during the time when infosec became a more widespread profession, a victim of its own success.
As an aside, a default install of PHP on reasonably modern Linux today is a hell of a lot more secure than it was in 2009. I know this because I did the comparison for a presentation to my peers in 2023.
This is the problem with extensible platforms that allow you the freedom to build what you want: their success is built on being malleable, which brings with it a lot of problems people with experience know to patch up, but less experienced people don't.
He’s right though. Didn’t know Lemmy was so pro PHP lol
When you have no idea what you are talking about, you post something like this
Its not 2005 anymore, not that PHP ever was a train wreck, but its not 2005 anymore. PHP has had a huge amount of improvements over the past two decades and I'll use it over anything else
A large percentage of sites use WordPress which uses PHP.
Outside of that, I've worked or consulted for 20-30+ companies across numerous industries and none of them used php or ever considered it.
“It’s wild to me people are still using PHP”
You must be isolated from development if you think PHP is not still everywhere.
it certainly hasn’t improved much since then.
I've heard the opposite talked about quite a bit.
Of course it's Primeagen. I haven't watched this particular video, but I've seen enough of his videos to know he's an idiot. I wouldn't trust anything he says about programming, at least half of everything he says is wrong.
Most of the things wrong with PHP can't be fixed, at least not without completely breaking all the existing PHP apps in such a fundamental way it would be tough to argue it's still the same language.


all 52 comments