<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on SakerWeb</title><link>https://www.sakerweb.com/blog/</link><description>Recent content in Blog on SakerWeb</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 25 Oct 2026 12:39:51 +0000</lastBuildDate><atom:link href="https://www.sakerweb.com/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>PHP2Shell &amp; SakerWeb</title><link>https://www.sakerweb.com/blog/php2shell-sakerweb/</link><pubDate>Sun, 25 Oct 2026 12:39:51 +0000</pubDate><guid>https://www.sakerweb.com/blog/php2shell-sakerweb/</guid><description>&lt;p&gt;It&amp;rsquo;s been a few days now since the news was awash with information about PHP2Shell, and how every PHP site in the world was vulnerable to it. That includes every WordPress site, and the SakerWeb console, but critically not any SakerWeb created sites.&lt;/p&gt;&#10;&lt;p&gt;You see, one of the key tenets of SakerWeb is that sites are hosted statically with no back-end code or database. This keeps the server immune to such vulnerabilities, and also able to cope with massive demand really easily because all it is doing is handing over files to web browsers - something it can do in its sleep.&lt;/p&gt;</description></item></channel></rss>