<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"  xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>HostFe.com - News</title>
<description>HostFe.com - News</description>
<link>https://hostfe.com/manage/?cmd=news</link>
<atom:link href="https://hostfe.com/manage/?cmd=news&amp;action=rss" rel="self" type="application/rss+xml" />
<item>
	<title>Critical PHP Security Vulnerabilities Patched Across All HostFe Servers</title>
	<link>https://hostfe.com/manage/?cmd=news&amp;action=view&amp;id=2</link>
        <guid>https://hostfe.com/manage/?cmd=news&amp;action=view&amp;id=2</guid>
	<pubDate>Thu, 22 Oct 2026 00:00:00 +0530</pubDate>
	<description><![CDATA[<p><strong>Security Update: CVE-2026-109618 &amp; CVE-2026-109619</strong></p>
<p><strong>Status: Security Patches Deployed | Severity: CRITICAL | CVSS Score: 9.2/10</strong></p>
<p>We are pleased to announce that HostFe has completed the deployment of critical PHP security patches across our hosting infrastructure, addressing two recently disclosed vulnerabilities identified as <strong>CVE-2026-109618</strong> and <strong>CVE-2026-109619</strong>, collectively known as <strong>"php2shell."</strong></p>
<p>These vulnerabilities were officially disclosed by the PHP Security Team on <strong>21 October 2026</strong> and carry a critical severity rating of <strong>9.2 under CVSS v4.0</strong>.</p>
<h3>Understanding the Security Threat</h3>
<p>The vulnerabilities could allow unauthenticated attackers to execute malicious code remotely on affected PHP environments.</p>
<ul>
<li>
<p><strong>CVE-2026-109618:</strong> Remote Code Execution (RCE) resulting from memory corruption during out-of-memory handling.</p>
</li>
<li>
<p><strong>CVE-2026-109619:</strong> Remote Code Execution (RCE) caused by stale internal PHP state being reused across requests.</p>
</li>
</ul>
<p>Both vulnerabilities potentially affect PHP-based websites and applications, including environments running Apache, PHP-FPM, LiteSpeed and other supported PHP execution handlers.</p>
<h3>Immediate Security Actions Taken by HostFe</h3>
<p>As part of our proactive infrastructure security strategy, HostFe implemented the following measures:</p>
<ul>
<li>
<p><strong>Critical Security Patching:</strong> Deployed the applicable vendor security updates across HostFe hosting servers.</p>
</li>
<li>
<p><strong>Early Preventive Hardening:</strong> On 20 October 2026, HostFe proactively disabled <code>session.upload_progress.enabled</code> as an additional precaution against known exploitation methods.</p>
</li>
<li>
<p><strong>PHP Security Updates:</strong> Applied applicable security releases and vendor-maintained backported fixes for supported PHP environments.</p>
</li>
<li>
<p><strong>Security Protection:</strong> Continued enforcement of server-level security policies, web application firewall protections and threat detection mechanisms.</p>
</li>
<li>
<p><strong>Infrastructure Monitoring:</strong> Continued monitoring for suspicious activity and potential exploitation attempts.</p>
</li>
</ul>
<p>The PHP Security Team has confirmed that disabling session upload progress mitigates certain known attack paths but does not eliminate every possible exploitation method. <strong>Installing the security updates remains the only complete solution.</strong></p>
<h3>PHP Security Release Versions</h3>
<p>The PHP project released the following patched versions on 21 October 2026:</p>
<table>
<tbody>
<tr>
<th>PHP Branch</th>
<th>Security Release</th>
</tr>
<tr>
<td>PHP 8.2</td>
<td>8.2.35</td>
</tr>
<tr>
<td>PHP 8.3</td>
<td>8.3.36</td>
</tr>
<tr>
<td>PHP 8.4</td>
<td>8.4.27</td>
</tr>
<tr>
<td>PHP 8.5</td>
<td>8.5.12</td>
</tr>
</tbody>
</table>
<p>For older PHP environments, security coverage depends on the operating system and PHP package provider. cPanel has released backported fixes for EA-PHP 7.4, 8.0 and 8.1, while CloudLinux is providing security updates for its ALT-PHP branches.</p>
<p>Customers using legacy PHP versions are strongly encouraged to migrate to currently supported releases wherever possible.</p>
<h3>Do HostFe Customers Need to Take Action?</h3>
<p><strong>No immediate server-level action is required for customers using HostFe-managed shared, cloud or reseller hosting services covered by this update.</strong></p>
<p>However, customers should continue following security best practices:</p>
<ul>
<li>
<p>Keep WordPress, plugins, themes, and other PHP applications updated.</p>
</li>
<li>
<p>Upgrade outdated PHP versions whenever application compatibility permits.</p>
</li>
<li>
<p>Remove unused or unsupported scripts.</p>
</li>
<li>
<p>Maintain independent backups of important website data.</p>
</li>
</ul>
<p>Customers operating self-managed dedicated servers remain responsible for verifying and applying updates within their own operating systems.</p>
<h3>Our Commitment to Hosting Security</h3>
<p>At HostFe, we believe that reliable hosting starts with a secure infrastructure.</p>
<p>Our engineering team continuously monitors emerging vulnerabilities, coordinates security updates and implements preventive safeguards to protect the websites and applications hosted on our network.</p>
<h3>Official Security References</h3>
<ul>
<li>
<p><a href="https://www.php.net/archive/2026.php#2026-10-21-5">PHP Official Security Advisory</a></p>
</li>
<li>
<p><a href="https://www.cve.org/CVERecord?id=CVE-2026-109618">CVE-2026-109618</a></p>
</li>
<li>
<p><a href="https://www.cve.org/CVERecord?id=CVE-2026-109619">CVE-2026-109619</a></p>
</li>
</ul>
<p><strong>Published:</strong> 22 October 2026<br/><strong>Category:</strong> Security Updates / Infrastructure Announcements</p>
<p><strong>HostFe Security &amp; Infrastructure Team</strong></p>]]></description>
</item>
<item>
	<title>Critical Security Advisory: UpdraftCentral Connection Key Compromise – What WordPress Site Owners Should Do Now</title>
	<link>https://hostfe.com/manage/?cmd=news&amp;action=view&amp;id=3</link>
        <guid>https://hostfe.com/manage/?cmd=news&amp;action=view&amp;id=3</guid>
	<pubDate>Tue, 20 Oct 2026 00:00:00 +0530</pubDate>
	<description><![CDATA[<h2 data-pm-slice="1 1 []">Overview</h2>
<p>HostFe is issuing an important security advisory following a confirmed security incident involving <strong>TeamUpdraft</strong>, the developer of the widely used WordPress backup plugin UpdraftPlus and its remote management platform, UpdraftCentral.</p>
<p>Between <strong>October 17 and 19, 2026</strong>, unauthorized access to TeamUpdraft's infrastructure potentially exposed sensitive account information and UpdraftCentral connection keys.</p>
<p>Security researchers subsequently identified attackers exploiting compromised connection keys to remotely install malicious plugins, create unauthorized WordPress users, and establish persistent backdoor access to affected websites.</p>
<p><strong>All HostFe customers using UpdraftPlus or UpdraftCentral are strongly advised to review their WordPress installations and take immediate precautionary action.</strong></p>
<h2>What Happened?</h2>
<p>UpdraftCentral allows WordPress administrators to remotely manage websites, perform updates, install plugins, and execute administrative tasks through authenticated connections.</p>
<p>Following the reported security breach, attackers obtained access to valid connection keys and used them to send unauthorized commands to connected WordPress websites.</p>
<p>These attacks could allow malicious actors to:</p>
<ul data-spread="false">
<li>
<p>Install unauthorized plugins containing malicious code.</p>
</li>
<li>
<p>Create hidden or unauthorized WordPress user accounts.</p>
</li>
<li>
<p>Obtain administrative capabilities without normal authentication.</p>
</li>
<li>
<p>Maintain persistent access to compromised websites.</p>
</li>
<li>
<p>Modify website files, configurations, or stored information.</p>
</li>
</ul>
<p>Importantly, <strong>this incident concerns compromised remote management credentials rather than a vulnerability in the UpdraftPlus plugin code itself.</strong></p>
<p>TeamUpdraft has confirmed that its official plugin downloads and self-hosted UpdraftCentral installations were not affected by this incident.</p>
<h2>Immediate Security Actions Required</h2>
<p>HostFe recommends that customers complete the following security checks immediately.</p>
<h3>1. Update UpdraftPlus</h3>
<p>Access your WordPress dashboard and navigate to <strong>Plugins &rarr; Installed Plugins</strong>.</p>
<p>Ensure UpdraftPlus is updated to at least:</p>
<ul data-spread="false">
<li>
<p><strong>UpdraftPlus Free:</strong> Version 1.26.13</p>
</li>
<li>
<p><strong>UpdraftPlus Premium:</strong> Version 2.26.13</p>
</li>
</ul>
<p>Install any newer security releases available.</p>
<p>These updates revoke affected older UpdraftCentral connections, helping prevent unauthorized commands through the compromised keys.</p>
<h3>2. Remove Existing UpdraftCentral Connection Keys</h3>
<p>Navigate to:</p>
<p><strong>WordPress Dashboard &rarr; Settings &rarr; UpdraftPlus Backups &rarr; Advanced Tools &rarr; UpdraftCentral</strong></p>
<p>Locate <strong>Manage existing keys</strong> and remove any existing connection keys.</p>
<p>Even if you do not actively use UpdraftCentral, verify that no connection keys are stored.</p>
<p>Removing UpdraftCentral connections does not disable the normal UpdraftPlus backup functionality.</p>
<h3>3. Inspect WordPress Users</h3>
<p>Navigate to <strong>Users &rarr; All Users</strong> and carefully review all accounts.</p>
<p>Pay particular attention to unfamiliar Administrator or Editor accounts. Security researchers have identified malicious accounts disguised as ordinary Editors while possessing elevated administrative capabilities.</p>
<p>Remove unauthorized accounts after preserving relevant evidence and verifying that they are not legitimate users.</p>
<h3>4. Inspect Installed Plugins</h3>
<p>Review all installed WordPress plugins, including Must-Use plugins and any recently added files.</p>
<p>Researchers have identified suspicious plugins using names such as <strong>Site Health Cache</strong>, alongside numerous other randomly generated plugin names.</p>
<p>Investigate unfamiliar plugins, especially those installed between October 18 and 19, 2026.</p>
<h3>5. Reset Passwords and Review Sessions</h3>
<p>Change passwords for WordPress administrators and your TeamUpdraft account.</p>
<p>Where appropriate, reset two-factor authentication, terminate existing sessions, and review other credentials accessible to the website.</p>
<h3>6. Scan Your Website for Malware</h3>
<p>Perform a comprehensive security assessment of your WordPress installation.</p>
<p>If suspicious activity is identified, isolate the affected website and investigate the extent of the compromise.</p>
<p><strong>Important:</strong> Updating UpdraftPlus does not automatically remove malicious plugins or unauthorized accounts that attackers may have installed before the connection keys were revoked.</p>
<h3>7. Restore From a Verified Clean Backup if Necessary</h3>
<p>If your website has been compromised, consider restoring it from a verified clean backup created before <strong>October 17, 2026</strong>.</p>
<p>After restoration, apply the latest security updates, revoke old connection keys, rotate affected credentials, and confirm that the website is clean before returning it to normal operation.</p>
<h2>Additional Advisory for UpdraftVault Users</h2>
<p>TeamUpdraft has also reset UpdraftVault connections as a precaution.</p>
<p>Customers using UpdraftVault should reconnect their remote backup storage and verify that scheduled backups are functioning correctly.</p>
<p>Customers relying on UpdraftClone should also review the vendor's instructions for replacing affected client keys.</p>
<h2>HostFe Security Advisory</h2>
<p>At HostFe, protecting hosting infrastructure and customer websites remains a key priority.</p>
<p>We strongly encourage all customers to maintain updated WordPress installations, regularly review administrative access, monitor installed plugins, and maintain independent, verified backups.</p>
<p><strong>Please note:</strong> This is a third-party security incident involving TeamUpdraft and does not, by itself, indicate a compromise of HostFe's hosting infrastructure.</p>
<p>Customers who identify unauthorized plugins, unfamiliar administrator accounts, or unexpected website modifications should immediately contact HostFe Technical Support through their client area.</p>
<h2>Official Security References</h2>
<p><strong>TeamUpdraft Security Incident Disclosure:</strong><br/><a href="https://teamupdraft.com/blog/security-incident-october-2026/" data-rich-text-autolink="">https://teamupdraft.com/blog/security-incident-october-2026/</a></p>
<p><strong>Patchstack Security Research:</strong><br/><a href="https://patchstack.com/articles/updraftcentral-key-compromise-wordpress-backdoors/" data-rich-text-autolink="">https://patchstack.com/articles/updraftcentral-key-compromise-wordpress-backdoors/</a></p>
<div><hr></div>
<p><strong>HostFe Security Team</strong></p>]]></description>
</item>
</channel></rss>