<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: bytepicks</title>
    <description>The latest articles on DEV Community by bytepicks (@bytepicks_058a57ec21bfcd5).</description>
    <link>https://dev.to/bytepicks_058a57ec21bfcd5</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4209224%2F0973bab4-25aa-463a-a918-2f76e8dd7693.png</url>
      <title>DEV Community: bytepicks</title>
      <link>https://dev.to/bytepicks_058a57ec21bfcd5</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/bytepicks_058a57ec21bfcd5"/>
    <language>en</language>
    <item>
      <title>LiteSpeed Cache Vulnerability: Check Your Version and Update to 7.9.1</title>
      <dc:creator>bytepicks</dc:creator>
      <pubDate>Sat, 31 Oct 2026 15:36:53 +0000</pubDate>
      <link>https://dev.to/bytepicks_058a57ec21bfcd5/litespeed-cache-vulnerability-check-your-version-and-update-to-791-1kg5</link>
      <guid>https://dev.to/bytepicks_058a57ec21bfcd5/litespeed-cache-vulnerability-check-your-version-and-update-to-791-1kg5</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://bytepicks.tech/litespeed-cache-vulnerability/" rel="noopener noreferrer"&gt;BytePicks&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Quick answer&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A &lt;strong&gt;LiteSpeed Cache vulnerability&lt;/strong&gt; disclosed on October 22, 2026 (CVE-2026-114190) lets an attacker who isn’t logged in access sensitive data on sites running &lt;strong&gt;version 7.9 or older&lt;/strong&gt;. The fix is &lt;strong&gt;LiteSpeed Cache 7.9.1&lt;/strong&gt; or later (the current version on WordPress.org is 7.9.2, released October 20, 2026). Go to &lt;strong&gt;Plugins&lt;/strong&gt; in your WordPress dashboard, check the version, and update. It takes two minutes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;CVE-2026-114190 at a glance&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Details&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Plugin&lt;/td&gt;
&lt;td&gt;LiteSpeed Cache for WordPress&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Type&lt;/td&gt;
&lt;td&gt;Sensitive data exposure&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Affected&lt;/td&gt;
&lt;td&gt;Version 7.9 and older&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Fixed in&lt;/td&gt;
&lt;td&gt;7.9.1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Login needed to exploit&lt;/td&gt;
&lt;td&gt;No (unauthenticated)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Severity&lt;/td&gt;
&lt;td&gt;CVSS 5.9 (medium)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Disclosed&lt;/td&gt;
&lt;td&gt;October 22, 2026, by Patchstack&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;LiteSpeed Cache is one of the most installed WordPress plugins. It often comes preinstalled on hosts that run LiteSpeed web servers, so plenty of site owners have it without ever having chosen it. That’s exactly why this one is worth five minutes of your time today.&lt;/p&gt;

&lt;p&gt;Here’s what was found, how serious it is, and the quickest way to make sure your site is patched.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is the new LiteSpeed Cache vulnerability?
&lt;/h2&gt;

&lt;p&gt;On October 22, 2026, &lt;a href="https://patchstack.com/database/wordpress/plugin/litespeed-cache/vulnerability/wordpress-litespeed-cache-plugin-7-9-sensitive-data-exposure-vulnerability" rel="noopener noreferrer"&gt;Patchstack published&lt;/a&gt; a sensitive data exposure flaw in LiteSpeed Cache, tracked as &lt;strong&gt;CVE-2026-114190&lt;/strong&gt; and found by researcher Ananda Dhakal. Every version up to and including 7.9 is affected. The developers fixed it in 7.9.1.&lt;/p&gt;

&lt;p&gt;“Sensitive data exposure” means the plugin can reveal information that should stay private. Patchstack hasn’t published the technical details, which is normal while sites are still updating, so we can’t say exactly what data is exposed. Don’t trust anyone who claims to know more right now.&lt;/p&gt;

&lt;p&gt;The part that matters most for you: &lt;strong&gt;no login is needed&lt;/strong&gt;. An attacker doesn’t need an account on your site. That’s why it’s worth patching even though the severity score is “medium.”&lt;/p&gt;

&lt;h2&gt;
  
  
  How serious is it?
&lt;/h2&gt;

&lt;p&gt;A CVSS score of 5.9 puts it in the medium range. It isn’t a “your site gets taken over” bug. But two things push it up the to-do list. It needs no login, so bots can try it against any site. And LiteSpeed Cache runs on millions of sites, which makes it an attractive target once details become public.&lt;/p&gt;

&lt;p&gt;Patchstack’s database also lists other recent LiteSpeed Cache issues, including a stored cross-site scripting flaw fixed earlier in 2026 (&lt;a href="https://cvefeed.io/vuln/detail/CVE-2026-3375" rel="noopener noreferrer"&gt;CVE-2026-3375&lt;/a&gt;, versions up to 7.7). If you haven’t updated this plugin in a while, you’re carrying more than one known bug.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to fix it, step by step
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Step 1: Check which version you have
&lt;/h3&gt;

&lt;p&gt;In your WordPress dashboard, go to &lt;strong&gt;Plugins → Installed Plugins&lt;/strong&gt; and find &lt;strong&gt;LiteSpeed Cache&lt;/strong&gt;. The version number sits under the plugin description. If it says 7.9.1 or higher, you’re already patched. Skip to step 4.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 2: Back up first (30 seconds)
&lt;/h3&gt;

&lt;p&gt;Updates almost never break anything, but a backup costs nothing. Most hosts have a one-click backup in their control panel, or you can use a backup plugin.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 3: Update the plugin
&lt;/h3&gt;

&lt;p&gt;Click &lt;strong&gt;Update now&lt;/strong&gt; under LiteSpeed Cache on the Plugins screen, or go to &lt;strong&gt;Dashboard → Updates&lt;/strong&gt;. If you manage the site from the command line, run:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;wp plugin update litespeed-cache
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Don’t see an update? Click “Check again” on the Updates page. Some hosts lock plugin versions, so ask your host if it still won’t appear.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 4: Purge the cache
&lt;/h3&gt;

&lt;p&gt;After updating, open &lt;strong&gt;LiteSpeed Cache → Toolbox → Purge&lt;/strong&gt; and click &lt;strong&gt;Purge All&lt;/strong&gt;. This makes sure visitors get fresh pages built by the new version.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 5: Test your site
&lt;/h3&gt;

&lt;p&gt;Open your homepage, a post, and any contact or checkout form in a private browser window. If something looks broken, purge again and clear your browser cache before panicking.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 6: Turn on auto-updates for this plugin
&lt;/h3&gt;

&lt;p&gt;On the Plugins screen, click &lt;strong&gt;Enable auto-updates&lt;/strong&gt; next to LiteSpeed Cache. For a widely targeted plugin, automatic security updates do more good than harm.&lt;/p&gt;

&lt;h2&gt;
  
  
  Do you even need LiteSpeed Cache?
&lt;/h2&gt;

&lt;p&gt;Only if your host runs a LiteSpeed web server. That’s where its page caching works. On Apache or Nginx hosting, most of its best features don’t apply, and a different caching plugin may suit you better. If you aren’t using it at all, deactivating and deleting it removes the risk entirely. An unused plugin is still attack surface.&lt;/p&gt;

&lt;p&gt;If you’re on LiteSpeed hosting, keep it.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to tell if your site was affected
&lt;/h2&gt;

&lt;p&gt;Because this flaw exposes data rather than letting attackers change your site, there may be nothing visible to find. Still, a quick check is sensible:&lt;/p&gt;

&lt;p&gt;Look for administrator accounts you don’t recognise under &lt;strong&gt;Users&lt;/strong&gt;. Check your host’s security emails and, if you use one, your security plugin’s activity log. And search Google for &lt;code&gt;site:yourdomain.com&lt;/code&gt; to spot spam pages you never published. If anything looks off, change your WordPress, hosting and database passwords and ask your host to scan the account.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Keep the rest of the stack patched too.&lt;/strong&gt; A plugin update doesn’t help if the server underneath is outdated. October also brought the critical PHP2Shell bugs in PHP itself. Our &lt;a href="https://bytepicks.tech/php2shell-wordpress/" rel="noopener noreferrer"&gt;PHP2Shell guide&lt;/a&gt; shows how to check that your host has patched PHP.&lt;/p&gt;

&lt;h2&gt;
  
  
  Simple habits that prevent the next one
&lt;/h2&gt;

&lt;p&gt;Most WordPress hacks don’t use clever new bugs. They use old bugs on sites that never updated. Turning on auto-updates for plugins you trust, deleting the ones you don’t use, and keeping a recent backup off your server covers the majority of real-world risk.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://patchstack.com/database/wordpress/plugin/litespeed-cache/vulnerability/wordpress-litespeed-cache-plugin-7-9-sensitive-data-exposure-vulnerability" rel="noopener noreferrer"&gt;Patchstack: LiteSpeed Cache &amp;lt;= 7.9 Sensitive Data Exposure&lt;/a&gt; (October 22, 2026)&lt;/li&gt;
&lt;li&gt;&lt;a href="https://patchstack.com/database/wordpress/plugin/litespeed-cache" rel="noopener noreferrer"&gt;Patchstack: LiteSpeed Cache vulnerability history&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://cvefeed.io/vuln/detail/CVE-2026-3375" rel="noopener noreferrer"&gt;CVE-2026-3375 (stored XSS, earlier 2026)&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>wordpress</category>
      <category>security</category>
      <category>webdev</category>
    </item>
    <item>
      <title>PHP2Shell (CVE-2026-109618/109619): patching PHP on VPS, Docker and mod_php</title>
      <dc:creator>bytepicks</dc:creator>
      <pubDate>Mon, 26 Oct 2026 16:46:31 +0000</pubDate>
      <link>https://dev.to/bytepicks_058a57ec21bfcd5/php2shell-cve-2026-109618109619-patching-php-on-vps-docker-and-modphp-4ofl</link>
      <guid>https://dev.to/bytepicks_058a57ec21bfcd5/php2shell-cve-2026-109618109619-patching-php-on-vps-docker-and-modphp-4ofl</guid>
      <description>&lt;p&gt;PHP2Shell at a glance&lt;/p&gt;

&lt;p&gt;Details&lt;br&gt;
CVEs    CVE-2026-109618 (out-of-memory corruption), CVE-2026-109619 (stale global state)&lt;br&gt;
Severity    CVSS v4.0 9.2 (critical), unauthenticated remote code execution&lt;br&gt;
Affected    Every PHP install serving web requests: PHP-FPM, Apache mod_php, php-cgi, LiteSpeed, FrankenPHP&lt;br&gt;
Fixed in    PHP 8.5.12, 8.4.27, 8.3.36, 8.2.35&lt;br&gt;
No official fix PHP 8.1 and older (end of life)&lt;br&gt;
Attacks seen    Yes, probing started before the patch was public&lt;br&gt;
On October 20, details of two serious PHP bugs leaked on social media, two days before they were supposed to be announced. The PHP team rushed out an emergency release the next afternoon. By then attackers had already started probing servers, and Amazon’s honeypots had logged an exploit attempt four days before anyone outside the disclosure group was supposed to know.&lt;/p&gt;

&lt;p&gt;Security researchers named the bugs PHP2Shell, because that’s what they give an attacker: a shell on your web server. If you run a WordPress blog, a WooCommerce store or anything else built on PHP, this one needs your attention this week.&lt;/p&gt;

&lt;p&gt;The good news: for most people on shared hosting the fix is already in place, or will be soon, and checking takes about 15 minutes. This guide explains what PHP2Shell is in plain English, how to tell whether your site is safe, and exactly what to do if it isn’t.&lt;/p&gt;

&lt;p&gt;What is PHP2Shell, in plain English?&lt;br&gt;
PHP is the programming language that runs WordPress. Every time someone opens a page on your site, the server starts a PHP process, sets up the request (reading form data, uploads, cookies), runs WordPress, and then cleans up. PHP2Shell is two separate mistakes in that setup-and-cleanup routine:&lt;/p&gt;

&lt;p&gt;CVE-2026-109618, out-of-memory corruption. If PHP runs out of memory halfway through setting up a request, some of its internal data is left half-built. The cleanup code then treats that broken data as if it were valid. A carefully crafted request can turn that confusion into code execution.&lt;br&gt;
CVE-2026-109619, stale global state. Some internal data outlives the memory it points to. The next request handled by the same PHP worker can then act on leftovers from the previous one. This is a classic use-after-free bug, and it is linked to PHP’s session upload progress feature, which is switched on by default.&lt;br&gt;
Both are rated 9.2 out of 10 on the CVSS v4.0 scale. What makes them so serious is the combination: no password, no plugin and no special configuration needed. According to PHP’s security team, on Apache with mod_php a single unauthenticated request can trigger the attack before any of your site’s code runs.&lt;/p&gt;

&lt;p&gt;Why WordPress sites are squarely in the blast radius&lt;br&gt;
Most WordPress vulnerabilities live in one plugin or theme, so only sites using that plugin are at risk. PHP2Shell is different. It sits in PHP itself, so it doesn’t matter which plugins you run, how strong your passwords are, or whether you’re on the latest WordPress version.&lt;/p&gt;

&lt;p&gt;That also explains why the usual WordPress security advice doesn’t help here:&lt;/p&gt;

&lt;p&gt;Updating WordPress core, themes or plugins doesn’t change PHP. PHP is server software, managed by your host or by you on a VPS.&lt;br&gt;
Security plugins can’t reliably block it. Wordfence, Solid Security and the like run inside WordPress. The bug triggers while PHP is still setting up the request, before WordPress or any plugin has loaded.&lt;br&gt;
Maintenance mode doesn’t help either. The request still reaches PHP.&lt;br&gt;
The only real fix is a patched PHP build, followed by a restart of PHP. Firewalls and config changes buy you time. They don’t replace the update.&lt;/p&gt;

&lt;p&gt;How PHP2Shell unfolded: the timeline&lt;br&gt;
Date (2026) What happened&lt;br&gt;
Oct 17  Amazon’s MadPot honeypots record a PHP2Shell exploit attempt from an anonymizing service, four days before disclosure.&lt;br&gt;
Oct 20  Bug details leak on social media ahead of the planned Oct 22 disclosure. PHP schedules an emergency release.&lt;br&gt;
Oct 21  PHP ships 8.5.12, 8.4.27, 8.3.36 and 8.2.35 at 14:00 UTC. CISA publishes an alert. Cloudflare rolls out WAF rules, including for free plans.&lt;br&gt;
Oct 22  Searchlight Cyber releases an open-source scanner. Hosts finish rolling out patched builds. Vendors such as Palo Alto Networks start confirming affected products.&lt;br&gt;
Oct 23  CISA updates its alert with detection rules. A third, related PHP issue (CVE-2026-115560) is disclosed, according to Hostinger.&lt;br&gt;
One caveat on “attacks in the wild”: security firms including watchTowr, Cloudflare and Amazon have reported exploit attempts, while CISA said at publication that it hadn’t yet seen a successful compromise. Don’t let that reassure you. Once a working exploit for a bug like this is out, mass scanning usually follows within days.&lt;/p&gt;

&lt;p&gt;Am I affected? A quick answer for each type of hosting&lt;br&gt;
PHP2Shell action chart: what to do on shared hosting, VPS, Docker, old PHP versions and static sites&lt;br&gt;
Who installs the PHP2Shell fix depends on where your site is hosted.&lt;br&gt;
Your setup  Who installs the fix    What you should do&lt;br&gt;
Shared hosting (Hostinger, Bluehost, SiteGround, etc.)  Your host   Confirm the patch is installed (Step 2). Upgrade off PHP 8.1 or older.&lt;br&gt;
Managed WordPress hosting   Your host   Same as shared: confirm, don’t assume.&lt;br&gt;
cPanel server you run yourself  You Update through EasyApache 4, then restart PHP-FPM / Apache.&lt;br&gt;
VPS or cloud server (DigitalOcean, Hostinger VPS, AWS, etc.)    You Update PHP packages and restart today (Step 3).&lt;br&gt;
Docker / containers You Rebuild on a patched PHP base image and redeploy.&lt;br&gt;
Static site, no PHP Nobody  Not affected.&lt;br&gt;
Step 1: Find your PHP version (2 minutes)&lt;br&gt;
In your WordPress dashboard, go to Tools → Site Health → Info, open the Server section and look at PHP version. Then compare it with this list:&lt;/p&gt;

&lt;p&gt;Your PHP branch Patched version Status&lt;br&gt;
8.5 8.5.12 or later Supported&lt;br&gt;
8.4 8.4.27 or later Supported&lt;br&gt;
8.3 8.3.36 or later Supported&lt;br&gt;
8.2 8.2.35 or later Security fixes end December 31, 2026&lt;br&gt;
8.1, 8.0, 7.4   No official release End of life: only host/vendor backports&lt;br&gt;
7.3 and older (incl. PHP 5) No fix at all   Upgrade now&lt;br&gt;
If your number is at or above the patched version, you’re done with this step. If it’s lower, don’t panic yet: many hosts and Linux distributions apply the fix to their own builds without changing the version number. That’s what Step 2 is for.&lt;/p&gt;

&lt;p&gt;Step 2: Confirm your host actually installed the patch&lt;br&gt;
On shared and managed hosting you can’t patch PHP yourself. Switching PHP versions in your control panel just moves you between builds your host already has. So the question is simply whether those builds are fixed.&lt;/p&gt;

&lt;p&gt;Two ways to check:&lt;/p&gt;

&lt;p&gt;Look at the PHP build date. Most panels have a “PHP Info” page (or you can see it in phpinfo()). A build date of October 21, 2026 or later is a good sign the fix is in. On Hostinger it’s under Websites → Dashboard → PHP Info.&lt;br&gt;
Ask support directly. Use the template below. “We have a firewall” isn’t the answer you’re after. You want “the patched PHP is installed and workers have been restarted.”&lt;br&gt;
Here’s a short message you can paste into your host’s live chat:&lt;/p&gt;

&lt;p&gt;Hi, I’d like to confirm my account is protected against PHP2Shell (CVE-2026-109618 and CVE-2026-109619). Can you confirm that (1) the PHP version my site uses has been updated to a patched build, (2) PHP workers have been restarted since the update, and (3) whether my PHP version is end-of-life and I should upgrade? My domain is: ______. Thanks!&lt;/p&gt;

&lt;p&gt;Where some big hosts stand (as of October 24):&lt;/p&gt;

&lt;p&gt;Hostinger says every plan except VPS was patched by October 22, across PHP versions 5.2 to 8.5, with extra firewall rules and session.upload_progress disabled server-wide. Shared, Cloud and cPanel customers don’t need to do anything. VPS customers do.&lt;br&gt;
cPanel (EasyApache 4) shipped fixed PHP 8.2 to 8.5 builds and backports for 7.4, 8.0 and 8.1. Hosts that depend on CloudLinux’s patched builds rolled out a little later.&lt;br&gt;
Other hosts are at different stages. If yours hasn’t posted a status page or emailed customers, ask.&lt;br&gt;
Step 3: On a VPS or your own server: update and restart&lt;br&gt;
If you manage the server, the clock is on you. Update PHP through your normal package manager (Ubuntu/Debian, AlmaLinux/Rocky, or your control panel’s updater). Distributions and LTS vendors got the patches before the public release, so packaged updates should already be available.&lt;/p&gt;

&lt;p&gt;Then the step people forget: restart every PHP process. PHP keeps running the old, vulnerable code in memory until it’s restarted. Restart PHP-FPM (for example sudo systemctl restart php8.3-fpm, adjusting the version) or Apache if you use mod_php. Then run php -v and check your site’s PHP Info page to confirm the new build is live.&lt;/p&gt;

&lt;p&gt;Can’t update right this minute? As a stopgap, set this in php.ini or your PHP-FPM pool config, then restart PHP:&lt;/p&gt;

&lt;p&gt;session.upload_progress.enabled = Off&lt;br&gt;
Hostinger notes that setting this with ini_set() in your code doesn’t work. It has to be in the server config. It also only blocks part of the attack surface: PHP itself says no configuration change fully mitigates these bugs. Use it to buy hours, not weeks.&lt;/p&gt;

&lt;p&gt;Running Docker? Your container keeps using whatever PHP was in its base image. Pull a patched php image, rebuild and redeploy. Restarting the old container changes nothing.&lt;/p&gt;

&lt;p&gt;Used the Remi repository? Reports on release day said rpms.remirepo.net hadn’t published updates yet. Check whether it has since, or switch to your distribution’s packages.&lt;/p&gt;

&lt;p&gt;Step 4: Stuck on PHP 8.1 or older? Upgrade now&lt;br&gt;
PHP 8.1 and earlier are end of life, so php.net didn’t ship official releases for them. There are minimal source patches for 7.4, 8.0 and 8.1, and some hosts and commercial vendors have backported fixes. But that’s a lifeline, not a plan. And PHP 8.2 itself stops getting security fixes on December 31, 2026, so if you’re upgrading anyway, go to 8.3 or 8.4.&lt;/p&gt;

&lt;p&gt;A safe upgrade routine for a typical WordPress site:&lt;/p&gt;

&lt;p&gt;Take a full backup (files and database), and keep a copy off the server.&lt;br&gt;
Update WordPress, every plugin and your theme. Old plugins are the most common reason a site breaks on newer PHP.&lt;br&gt;
Switch PHP to 8.3 or 8.4 in your hosting panel. On Hostinger that’s Websites → Dashboard → PHP Configuration.&lt;br&gt;
Test the pages that matter: homepage, a post, contact form, checkout if you sell anything, and the admin area.&lt;br&gt;
If something breaks, switch back, find the plugin causing it (deactivate plugins one at a time), and replace or update it.&lt;br&gt;
New to hosting panels? Our guide to starting a blog with Hostinger walks through the dashboard step by step.&lt;/p&gt;

&lt;p&gt;Step 5: Check for signs that someone got in&lt;br&gt;
If your server ran an unpatched PHP between October 17 and the day it was fixed, spend ten minutes looking for warning signs:&lt;/p&gt;

&lt;p&gt;Unknown admin users. Go to Users and filter by Administrator.&lt;br&gt;
Plugins you didn’t install, especially ones with generic names.&lt;br&gt;
PHP files in your uploads folder. wp-content/uploads should hold images and documents, never .php files.&lt;br&gt;
Spam pages in Google. Search site:yourdomain.com and look for casino, pharmacy or foreign-language pages you never wrote.&lt;br&gt;
Google Search Console → Security &amp;amp; Manual Actions → Security issues.&lt;br&gt;
Emails from your host about malware, spam sending or unusual resource use.&lt;br&gt;
On a VPS, also check whether your PHP worker processes have been launching shells or downloading files. CISA specifically names this as something to watch for, and has published detection rules for it.&lt;/p&gt;

&lt;p&gt;If anything looks off, don’t just delete the suspicious file. Ask your host to scan the account, restore a backup from before the infection, then change every password: WordPress, hosting, database and FTP/SFTP.&lt;/p&gt;

&lt;p&gt;Do a firewall and Cloudflare help?&lt;br&gt;
Yes, as a short-term shield. Cloudflare deployed WAF rules against known PHP2Shell exploit patterns for all customers, including the free plan, and CISA says a web application firewall “may offer some protection” until you patch. If your site already runs through Cloudflare, that’s a useful extra layer.&lt;/p&gt;

&lt;p&gt;But WAF rules only match attack patterns someone has already seen. Attackers tweak their requests, and Cloudflare’s own CTO described the protections as temporary. Treat the firewall as a seatbelt, not as the fix.&lt;/p&gt;

&lt;p&gt;The AI angle: why this bug is different&lt;br&gt;
According to BleepingComputer, researchers at Calif, OpenAI and Wiz found the bugs. Wiz said the flaws had been sitting in PHP for a very long time, and that exploiting them used to require a long, complex chain of steps. In their words, “Frontier AI models substantially reduced that barrier, turning a longstanding flaw into an exploit.”&lt;/p&gt;

&lt;p&gt;That’s the part worth thinking about beyond this week. AI tools are making it faster to find and weaponize old bugs in software everyone depends on. For site owners, the practical lesson isn’t fear. It’s to make “how fast does my host patch?” part of how you pick hosting, next to price and speed. It’s also one more reason not to leave sites on end-of-life PHP versions for years.&lt;/p&gt;

&lt;p&gt;If you’re comparing hosts, our Hostinger review is a good place to start, and our explainer on AI agents covers how these tools work and where they fall short.&lt;/p&gt;

&lt;p&gt;The 15-minute PHP2Shell checklist&lt;br&gt;
Five steps to check and fix PHP2Shell on a WordPress site, with patched PHP versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35&lt;br&gt;
Save or share this checklist.&lt;br&gt;
Check your PHP version in Tools → Site Health → Info → Server.&lt;br&gt;
Confirm the PHP build date is October 21, 2026 or later, or get written confirmation from your host.&lt;br&gt;
On a VPS: update PHP, restart PHP-FPM/Apache, verify with php -v.&lt;br&gt;
If you can’t update yet: disable session.upload_progress in server config and put the site behind a WAF.&lt;br&gt;
On PHP 8.1 or older: back up, update plugins, move to PHP 8.3 or 8.4.&lt;br&gt;
Look for unknown admins, stray plugins and .php files in uploads.&lt;br&gt;
Make sure you have a recent backup stored somewhere other than your server.&lt;br&gt;
Bottom line&lt;br&gt;
PHP2Shell is about as serious as web server bugs get: unauthenticated, remote and present on nearly every PHP site. It’s also one of the easier ones to close. If you’re on decent shared or managed hosting, like Hostinger, which says all its non-VPS plans were patched by October 22, the fix is probably already in. A two-minute check confirms it. If you run your own server, update PHP and restart it today. Don’t wait for the weekend.&lt;/p&gt;

&lt;p&gt;This story is still developing. Vendors are confirming affected products and PHP has disclosed a related issue, so we’ll update this guide as new details come in.&lt;/p&gt;

</description>
      <category>php</category>
      <category>security</category>
      <category>devops</category>
      <category>wordpress</category>
    </item>
  </channel>
</rss>
