php2shell: how are you confirming which PHP your web traffic actually runs on?

Leader ●4 ●12 ●65
calendar_today ago • schedule1 min read

PHP's 21 October fixes (8.5.12 / 8.4.27 / 8.3.36 / 8.2.35) cover two critical runtime flaws. Because they sit below the application, updating a CMS or framework doesn't help — the runtime has to change and workers have to restart.

The step I'd expect to trip teams up is inventory. php -v on a shell tells you about the CLI, not necessarily what PHP-FPM, mod_php or a bundled appliance is serving.

What are you using to answer "where does PHP run and is it patched?" — package queries, phpinfo() behind auth, image scanning, something else? And has anyone found a clean way to confirm old FPM workers are gone after the upgrade?

Write-up with versions, interim settings and detection signals: https://dev.to/_firelinks/php2shell-a-request-that-fails-halfway-still-leaves-state-behind-5877

1 Comment

0 votes
🔥 Join developers growing publicly
Share your knowledge, build in public, and grow your developer presence with a global community.

More Posts

Your AI Doesn't Just Write Tests. It Runs Them Too.

Kevin Martinez - May 12

Cisco's Amy Chang: A Model's "Passport" Doesn't Tell You Where It Actually Came From

Tom Smithverified - Aug 27

MCP Is the USB-C of AI. So Why Are You Plugging Everything In?

Ken W. Algerverified - Jun 10

How to Build a Portfolio Website That Actually Gets You Hired

muhammadfarhan.dev - Aug 21

Attention-Free Score: How Domain Reports Show Which Pages Need Work

ApogeeWatcherverified - Sep 1
chevron_left
2.9k Points • 81 Badges
Toronto, ON • michaeldabydeen.com
7Posts
158Comments
11Connections
I split my time between enterprise APIs, decentralized systems, and teaching at Sheridan and Conesto... Show more

Related Jobs

View all jobs →

Commenters (This Week)

2 comments
1 comment
1 comment

Contribute meaningful comments to climb the leaderboard and earn badges!