Wednesday, 18 November 2026

The PHP security vulnerabilities that put the internet on notice

As of October this year, a couple of newly discovered PHP vulnerabilities threatened to rattle the Internet. The PHP2Shell vulnerability was found to have existed for the past decade, undisclosed until recently. Any PHP that's 5.4 and above is vulnerable.

For this particular vulnerability, the problem is not with insecure code. It's with PHP itself. In layperson-speak: We've been installing perfectly respectable locks on the doors, only to discover that the hinges were compromised.

Good lock, bad hinges.

Despite its flaws, PHP still runs more than seventy percent of the world's websites. That's just websites we're talking about - not interfaces such as system panels and software applications.

The bug was recently found with the help of AI, but there have been reports that even before the reported discovery, there have been signs that this vulnerability was already being probed. Which is... not a comforting thought. This bug had not been officially disclosed for the past ten years. Does that mean that seventy percent of the internet has been vulnerable for the past ten years? Damn.

My own PHP use

I have fond memories of PHP. It's what I cut my teeth on after ASP, and what sparked my career revival in the 2010s. Still, I've never been blind to its faults. I've just been extremely tolerant. Kind of like Mrs TeochewThunder - I have a soft spot for her, but boy does she annoy me sometimes.

I haven't used PHP at work in a while. These days it's JavaScript, and sometimes Python.

My personal site still runs on PHP. Recently I jacked it up from 5.6 straight to 8.5.12. Daring of me, until you consider that most of my code was future-proofed to begin with (PDO instead of MySQLi, careful array declarations, etc) and had no fancy features that would require concern on my part.

And just as I upgraded, this happened. 8.5.12 just happens to be one of the releases of PHP that have been patched. Why aren't I this lucky with the lottery?

Patched!

My hosting provider is taking care of the security patches. Hey, I'm paying for the privilege. What, you think this blog is free? I'm a cheap bastard, but not that cheap. The alternative is to get my site off my provider and host it myself and provide my own patches... did I mention I'm lazy in addition to cheap?

Conclusion

I wouldn't read too much into this development. For NodeJS, there's the Node2Shell vulnerability. In 2021, there was Java's Log4Shell. This just happened to be PHP's turn. 

EDITOR'S NOTE: These issues aren't equivalent. I picked them because of the similar "shell" naming convention.

PHP haters will crow that this is just another reason to avoid PHP, but if we're being honest, PHP is hardly unique in this regard. 


Shell-om, my friends!
T___T

No comments:

Post a Comment