Sounds like a reminder to (a) migrate off PHP wherever possible, and,
“The vulnerabilities can allow unauthenticated attackers to execute code on affected servers or read sensitive process memory,” Wiz writes in its research. “That memory may contain passwords, authentication tokens, API keys and certificates belonging to other requests or the server itself.”
Keep your server processes sandboxed / running as a dedicated user.
And if you don’t actually need dynamic rendering (looking at most WordPress installations), use a static site generator (Jekyll, Hugo, etc).
I seriously wonder how PHP got so popular. It has never been a paragon of … anything from a serious engineer perspective.
Really because it was easier to deal with than Perl in the early days, and those were basically your choices.
Because it’s easy. Just do some HTML markup and some CSS and slap some
inline. This is partially the same reason why there are so many horribly outdated versions “in production”.
Low bar of entry compared to everything else back in the day. Also quite fast being written in C. Then Laravel came around and it exploded in popularity. And of course you have WordPress that back in the day allowed everyone to get a site up and running. Not just blogs, due to the vast amount of plugins. There are more, butI think those are the biggest reasons.
And if not full static generation then a light dynamic option like Alpine.js
That wouldn’t have helped much, because the vulnerability was in the server’s handling of POST (I think specifically multipart) requests.
What ridiculous percentage of the internet runs on Wordpress still? Maybe it’s less now that AI floods everything with everything. But you gotta know so many of those sites are not updating any time soon
Supposedly 40% of all websites as of 2025 use it in some form https://w3techs.com/technologies/details/cm-wordpress
