Stephen Rees-Carter

@valorin.bsky.social

Friendly Hacker, Speaker, and PHP & Laravel Security Specialist.🕵️ I write securinglaravel.com and hack stuff on stage for fun. 😈 I'm found elsewhere too: https://pinkary.com/@valorin 🪄

Didn’t want to shill my stuff during the chaos or in my Security Notices, but now things have calmed down (I hope!): I do Laravel & PHP Security Audits & Pentests. If PHP2Shell has you wondering what’s hiding in your own apps, I can help. valorinsecurity.com

Laravel Security Audits and Penetration Tests – Stephen Rees-Carter

Looking for a Laravel Security Audit and Pentest? I'm Stephen Rees-Carter and I'm excited to work with you to secure your site, and keep it safe!

valorinsecurity.com

How'd we all go overnight? I'm catching up on everything that's happened since my last and will put together an article with all the details I can find, if you want to know more about *waves hands* this. Let's agree to not do this again for a while, yeah?

Ok folks, I'm switching off for the night. It's after 3am here and I need to do the school run in a few hours. Good luck to everyone still updating servers and untangling updates! Hopefully it's a quiet night of updates and checking version numbers. 🤞

for others reading this: securinglaravel.com/laravel-secu... Instead of waiting for the 22.04 and 24.04 updates to land in the Launchpad PPA, you can switch repos to the version here: packages.sury.org/php/README.txt This is confirmed by the Laravel team as safe for Forge servers.

Laravel Security Notice: Critical PHP Security Release ⚠️

[Notice #5] A Critical PHP Security Release is coming very soon - you need to be ready to patch your servers.

securinglaravel.com

Honestly, it's pretty disappointing to see responsible disclosure fail like this. It takes a lot of effort to release a critical patch. Leaking the announcement or publishing a PoC before a scheduled patch shows you have no ethics and are only interested in credit for yourself.

Not a bad view to write a new In Depth article. 😎 I'm doing a walkthrough of the results from Claude's security plugin on one of my projects, looking at the quality of the findings and how we can identify the real risks from the noise.

Bild

How does everyone feel about pentest findings/reports available online (behind auth), as opposed to emailed or sent via Slack/Teams? I've always been wary of putting them online, even behind auth, but I can see some benefits - especially with agents doing the remediation work.

Just scheduled my next Security Tip. Feels nice to be scheduling them in advance again, rather than posting late! 😎 This is a rather fun one too: a story from a recent pentest where the client's defences caught me!

How can you level up as a PHP / Laravel focused web developer in a world where software engineering becomes increasingly focused on security? Step 1: Sign up to @valorin.bsky.social's Securing Laravel newsletter. Congrats on an epic 5 years Stephen! Still some of the best content on the topic.

Submitted my first CVEs directly to MITRE due to an unresponsive package maintainer for a very popular package that sits at #5 for a common search term on Packagist. Will be interesting to see how this goes.

One of the most satisfying (and most frustrating!) parts of pentesting is spending an hour setting up the perfect PoC, composing shock-value screenshots, and writing a succinct report - only for them to spend 30 seconds making a trivial code change that fixes the issue. 😈😱