Techdome
All editions

PHP2Shell checks, queues, webhooks, and new work

Security notes, backend architecture posts, anonymised case studies, and new n8n templates.

Oct 28, 2026 · 2 min read

PHP2Shell checks, queues, webhooks, and new work

This edition is mostly about backend edges: how work moves between systems, how repeated deliveries stay safe, how APIs get tested, and how to respond when a PHP vulnerability needs attention. We also published four anonymised work pages and a set of n8n templates by Rahul Joshi on n8n.io.

Lead story: checking and protecting PHP sites

We published PHP2Shell: how to check and protect your PHP site, covering PHP2Shell, tracked as CVE-2026-109618 and CVE-2026-109619. The post is about the practical response: check your PHP version, patch it where possible, or shield it with a WAF when patching is not immediate.

The useful part of this kind of incident work is reducing ambiguity. Teams need to know which PHP versions are in use, which hosts are exposed, and whether the current mitigation is a patch or a protective control in front of the application. The post keeps the focus on those checks rather than on general vulnerability commentary.

It also includes two real cases. The point is not that every PHP estate looks the same, but that the response pattern should be concrete: identify exposure, decide on patching or shielding, and avoid leaving the system in a half-known state.

In brief

New n8n templates

If one of these topics maps to a system you are building or maintaining, you can talk to our engineers.