This PHP vulnerability has been refreshing. It’s exposed just how many high-follower-count cybersecurity “experts” can’t distinguish between an insecure language and insecure code written in that language.
A large following clearly doesn't guarantee technical competence.
Turbo Intruder 2 has landed! You can now surpass 100,000 RPS over WiFi using the new HTTP/3 engine, test HTTP/3 exclusive targets with the Burp adapter, and deploy new research-grade race condition techniques! Check out the post below for full details:
@njcve_ Yeah I imagine you've got to be on the important list for that 😢 Not sure what triggered for me, I had it in a loop building some labs and got like 15 out of 40 in and then it refused to do any more. Must hit some kind of internal limit for security related input.
@njcve_ Ah okay, I was doing loads of security stuff ( not offensive ) with GPT 6 and after a few hours it suddenly started telling me I needed daybreak, uploaded verification and got it straight away. Annoyingly it uses 5.6 and now not getting the results that 6 was giving me.
People who say PHP is insecure are uninformed, and I'll happily have a healthy debate in the replies.
The reputation comes from the 90s and early 2000s, when PHP powered most of the web and security was an afterthought everywhere. People who cut their teeth hacking those sites still feel the flinch when they see PHP.
Modern PHP ships with secure primitives out of the box, like prepared statements via PDO and built-in password hashing. Frameworks like Laravel go further and escape output by default. And these days you often can't tell a site is running PHP at all, most frameworks route away from the .php extension now.
Before you throw a jab at a language, framework, or any technology, try testing it first. Then let's have a wholesome argument.
Is this an LSD flashback or did a person dressed as a red elephant called Welephant used to come into your school to teach you about not starting fires?
The tech in this series is awful, I remember it being quite good in the first series apart from in the final episode when the analyst finally realised it was base64 encoded which anyone could spot in a second 🙄