<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on Scott Tactical</title><link>https://scotttactical.com/tags/security/</link><description>Recent content in Security on Scott Tactical</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 24 Oct 2026 12:00:00 -0700</lastBuildDate><atom:link href="https://scotttactical.com/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>An Unpatched RCE on a Church Website: Moving It Off an End-of-Life Host</title><link>https://scotttactical.com/wordpress-to-home-k8s/</link><pubDate>Sat, 24 Oct 2026 12:00:00 -0700</pubDate><guid>https://scotttactical.com/wordpress-to-home-k8s/</guid><description>&lt;p&gt;A parish church website was running on a single cloud droplet with a stack that had quietly gone end-of-life: PHP 7.3, WordPress 6.6.2, MariaDB 10.4. That part is common. What made it urgent was the 2026 &amp;ldquo;php2shell&amp;rdquo; set of pre-auth PHP remote-code-execution vulnerabilities (&lt;code&gt;GHSA-w8hw-w9fx-j79w&lt;/code&gt;, &lt;code&gt;GHSA-6wmf-4rv5-p3rp&lt;/code&gt;). On a supported PHP there is a patch. On PHP 7.3 there is no patch, because 7.3 is past end-of-life and upstream stopped shipping fixes. The only real remediation was to get off that stack entirely.&lt;/p&gt;</description></item></channel></rss>