Your business website could be running the latest version of WordPress and still have a serious security problem. Hackers are exploiting two flaws in PHP, the software working behind millions of websites. The flaws, known as PHP2Shell, can let criminals run commands on certain servers without signing in. Emergency fixes are available. Many website owners still don’t know which PHP version their hosting company uses, much less whether it’s patched.
PHP2Shell Attacks Are Underway
The Cybersecurity and Infrastructure Security Agency (CISA) has added CVE-2026-109618 and CVE-2026-109619 to its Known Exploited Vulnerabilities catalog. Both flaws have a critical severity score of 9.2 out of 10. They involve errors in how PHP handles memory during website requests. On certain servers, an attacker can use these errors to run commands without signing in, an attack known as remote code execution.
The key dates:
| Date | What Happened |
|---|---|
| October 21 | PHP released emergency security fixes for both vulnerabilities. |
| October 24 | Three deliberately vulnerable test servers recorded 35 successful command-shell launches. |
| October 26 | CISA added both flaws to its catalog of known exploited vulnerabilities. |
Those test servers were designed to make exploitation easier. SecurityWeek’s reporting on PHP2Shell attacks explains the limited test setup. The findings show working techniques, not their reliability against ordinary business websites.
Why WordPress Updates Aren’t Enough
You sign in to WordPress, update the plugins, check the theme and get back to work. That routine is worth keeping, but it doesn’t necessarily update PHP. WordPress is the application you use to manage your website. PHP is the software underneath it, and your hosting company often controls that part.
WordPress can report everything current while the server still runs a vulnerable PHP release. On shared hosting, customers may not even have permission to make that change themselves. The risk also reaches online stores, customer portals and booking systems built with PHP. The official WordPress hosting requirements confirm that the platform depends on PHP. Some server setups, especially those using Apache mod_php, have been shown to be particularly exposed, although other configurations also need patching.

How Many Websites Could Be Affected?
PHP runs everything from small company pages to busy online stores. Researchers at Palo Alto Networks Unit 42 identified more than 22.6 million exposed instances that might be vulnerable to PHP2Shell. That means possible exposure, not confirmed breaches or unpatched websites. Server settings and vendor security fixes determine the actual risk.
Some early breach claims have also changed. Unit 42 withdrew an earlier claim linking a government-agency intrusion to PHP2Shell after researchers could not confirm how the attackers first gained access. Working exploits have been observed on test servers, but there is no reliable count of business websites compromised through these flaws.
What Hackers Could Do to Your Website
A successful attack may let someone run commands with the permissions given to the server’s PHP process. That isn’t always full administrator access, but it can still be enough to cause trouble. If PHP can read a sensitive file or change part of a website, the attacker may be able to do the same. The damage depends on the server’s permissions and other security controls. Possible consequences include:
- Exposed information. Someone might read accessible configuration files, stored credentials or customer records.
- Changed website content. Attackers could insert malicious code, alter pages or send visitors to fake websites.
- Business disruption. Changes to files or services could interrupt payments, online orders and customer forms.
These are possible outcomes, not evidence that a particular website has been breached. In its PHP2Shell threat assessment, Sophos reported seeing scanning and unsuccessful attempts against systems it monitored. Its researchers had initially suspected successful exploitation, but corrected that assessment after further investigation. Attempted attacks and confirmed breaches are not the same thing.
PHP Versions Affected by PHP2Shell
The PHP team released emergency updates on October 21, 2026. According to the official PHP security release announcements, these are the first releases containing fixes for both vulnerabilities:
| PHP Branch | First Fixed Version |
|---|---|
| PHP 8.5 | 8.5.12 |
| PHP 8.4 | 8.4.27 |
| PHP 8.3 | 8.3.36 |
| PHP 8.2 | 8.2.35 |
Earlier releases in these branches need attention unless the host has installed an equivalent security patch. PHP 8.1 and older no longer receive routine fixes from the PHP project, although some Linux distributors and support providers patch older builds themselves. A version number can be misleading. Ask which security package covers both flaws and whether the affected PHP services were restarted or reloaded after installation. PHP 8.2 also reaches the end of security support on December 31, 2026, making an upgrade plan especially important.
How to Check Your Website’s PHP Version
WordPress owners can check their PHP version in the dashboard without installing anything. The WordPress Site Health documentation covers the same screen. Here’s where to look:
- Sign in to WordPress and open Tools > Site Health.
- Select Info, then expand Server.
- Find the PHP version entry and compare it with the fixed releases above.
On another website platform, try your hosting control panel or ask the company that manages the site. Remember, this number is a starting point, not a final verdict. It may not show a vendor’s backported fix, another PHP installation on the account or a service that failed to restart. Before changing versions yourself, back up the website files and database. Then test checkout pages, contact forms and customer sign-ins, since older plugins and custom features can have compatibility problems.

What to Ask Your Hosting Provider
You shouldn’t have to become a server expert to get a clear answer. Ask your hosting company whether both CVE-2026-109618 and CVE-2026-109619 have been fixed for your website. Request the PHP version or vendor patch details, when the update was installed and confirmation that the affected services restarted. A general promise that the platform is secure doesn’t answer those questions.
Ask about suspicious activity as well. CISA’s PHP security alert recommends watching for PHP worker processes launching command shells or downloading tools. Your provider can also check unusual crashes, file changes and outbound connections. Such activity is not proof of a breach, but it deserves a closer look. If customer support cannot confirm the fixes, ask for someone on the technical or security team.
PHP2Shell Security Checklist
You can start without command-line access. Track what your host confirms and follow up on unresolved issues. Google Cloud’s PHP2Shell security analysis emphasizes patching and monitoring. Firewalls can reduce exposure, but they do not repair the underlying flaw. Here is what to check:
- Confirm both fixes. Get written confirmation that the two PHP2Shell vulnerabilities have been addressed for your site.
- Check the restart. Ask whether affected PHP processes restarted or reloaded after the patch was installed.
- Keep a separate backup. Save files, databases and settings away from the server, and make sure the backup can be restored.
- Review server activity. Have your host investigate unusual commands, unexpected changes and suspicious requests.
- Test important features. Check payments, bookings, contact forms and logins after the update.
- Maintain other defenses. Update WordPress components, turn on multifactor authentication and consider a web application firewall.
If an affected service cannot be patched promptly, ask your provider about taking it offline until it can be fixed. That can disrupt business, but leaving a critical flaw exposed also carries serious risk. A firewall cannot replace the update.
What to Do If You Suspect a Breach
An unfamiliar administrator account, an unexpected redirect or an unexplained PHP file change deserves attention. None of these signs proves PHP2Shell was involved. Stolen passwords and vulnerable plugins can cause similar trouble, so the first step is finding out what happened. Contact your host or a qualified security specialist and explain what changed and when you first noticed it.
Preserve logs and suspicious files when possible, but do not delay action needed to stop an active attack. Investigators may need that evidence to determine what was changed and whether customer information was exposed. The NIST resources for responding to a cyber incident can help smaller organizations plan their response. Installing a patch closes the two known flaws, but it cannot remove malware, replace stolen passwords or reverse earlier damage.
Common Questions About PHP2Shell
Is Every WordPress Website Vulnerable?
No, exposure depends on the server’s PHP installation, security patches and setup. Even an updated WordPress site may still need a separate PHP fix from its host.
Can Attackers Get In Without a Password?
Yes, the flaws can let attackers run commands without signing in on some vulnerable servers. That doesn’t mean every attempt succeeds or every PHP website can be breached this way.
Will a WordPress Security Plugin Stop It?
A plugin cannot repair a flaw in PHP itself. A firewall might block certain requests, but the proper PHP security update is still needed.
Does Updating PHP Remove Existing Malware?
No, an update does not automatically remove malicious files or access left behind by an attacker. A possible breach needs its own investigation and recovery plan.
What If My Host Uses an Older PHP Release?
Ask whether a supported vendor has installed fixes for both vulnerabilities in that release. If not, the host should explain when the site can move to a corrected version.
Website Security Beyond WordPress
PHP2Shell exposes a frustrating gap in website maintenance. You can keep WordPress and every plugin updated, yet still depend on a server running vulnerable software. A normal homepage and a clean-looking dashboard cannot tell you whether PHP is patched, especially when your hosting company manages it behind the scenes.
At JENI® Systems, we encourage business owners to get clear answers from their hosting provider, confirm that both fixes are installed and investigate unusual activity. Do not assume your website has been hacked, but make sure it has not been left exposed.
Related Articles
Website Security Basics for Small Businesses
Learn how software updates, access controls, backups, and monitoring help protect your business website, customer information, and daily operations.
CISA Security Alerts: XWiki and VMware Flaws
Discover why CISA flags actively exploited security flaws, how attackers target vulnerable software, and why timely security patches matter.
WordPress Casino Spam: Signs and Cleanup
See how hackers hide spam and redirects on compromised WordPress sites, which warning signs to watch for, and how cleanup helps protect search rankings.
What to Do in the First Hour of a Cyberattack
Learn how to respond to a suspected cyberattack, limit unauthorized access, preserve important evidence, and organize your first recovery steps.
