<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Hosting-Security on kalfaoglu.net</title><link>https://blog.kalfaoglu.net/tags/hosting-security/</link><description>Recent content in Hosting-Security on kalfaoglu.net</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 15 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.kalfaoglu.net/tags/hosting-security/index.xml" rel="self" type="application/rss+xml"/><item><title>WHMCS Unauthenticated RCE Still Unpatched on Many Servers: CVE-2026-67399 and CVE-2026-67398</title><link>https://blog.kalfaoglu.net/posts/2026-11-15-whmcs-cve-2026-67399-rce-pii-en/</link><pubDate>Sun, 15 Nov 2026 00:00:00 +0000</pubDate><guid>https://blog.kalfaoglu.net/posts/2026-11-15-whmcs-cve-2026-67399-rce-pii-en/</guid><description>&lt;p&gt;The September patch cycle brought an uncomfortable surprise for WHMCS administrators: an unauthenticated remote code execution flaw classified as critical. Two months later, unpatched installations are still a common sight.&lt;/p&gt;
&lt;h2 id="what-was-fixed"&gt;What was fixed&lt;/h2&gt;
&lt;p&gt;WHMCS released versions 9.0.8 and 8.13.7 on September 3, 2026, addressing two separate vulnerabilities. Both were disclosed in &lt;a href="https://help.whmcs.com/m/125386/l/2118034-cve-2026-67399-whmcs-security-update-2026-09-03"&gt;vendor security advisories&lt;/a&gt; on the same day.&lt;/p&gt;
&lt;h2 id="cve-2026-67399--unauthenticated-rce"&gt;CVE-2026-67399 — Unauthenticated RCE&lt;/h2&gt;
&lt;p&gt;The nastier of the two. WHMCS describes it as a flaw in WHMCS 8.0.x and later &amp;ldquo;involving the submission of forged payloads without adequate restrictions.&amp;rdquo; Under the right conditions, an unauthenticated attacker — no login needed, no account required — can execute arbitrary code on the server hosting WHMCS, resulting in complete compromise of the installation and all its data.&lt;/p&gt;</description></item></channel></rss>