Security alert: critical PHP flaws, exploitation observed in the wild. Check your exposure
PHP2Shell · Critical alert
Your PHP website can be taken over. No password needed.
On 21 October 2026, PHP shipped emergency fixes for two critical flaws that let attackers run their own code on web servers, no login required. Exploitation attempts are already being observed. Not updated since? Assume you’re exposed.
Opens your email app with a short pre-filled message. Two minutes, no obligation.
- 24x7 Security Operations Center
- 1000+ organizations served in 32 countries
- Microsoft Azure Expert MSP
9.2/10
Critical severity score for both flaws
69.3%
of websites with a known server-side language run PHP
1 in 3
PHP websites still run PHP 7 or older (34.6%), with no official fix coming
$4.99M
global average cost of a data breach in 2026, a record high
Why it matters
The flaw is in PHP itself. Your code can’t protect you.
WordPress, Drupal, Laravel or custom-built: it makes no difference. Every PHP application on an unpatched server is exposed, because the attack targets PHP’s own request handling, not your application code.
- 1
A crafted request arrives
No login and no clicks. Just a malicious web request sent to your site.
- 2
PHP’s memory is corrupted
The bug lives in how PHP handles requests and memory, and it can fire before your application code even runs.
- 3
The attacker’s code runs
With your website’s own access: its files, its configuration and its database credentials.
What an attacker can do next
Steal your data
Customer records, orders and credentials can be copied out quietly.
Leave a backdoor
Hidden web shells, scheduled tasks and new accounts let attackers return, even after you patch.
Hijack your visitors
Injected scripts can skim payments or spread malware from your trusted domain, until browsers flag it as dangerous.
Start the regulatory clock
Under GDPR, a reportable personal-data breach must be notified to regulators within 72 hours where feasible.
The trap most teams fall into
Patching closes the door. It doesn’t tell you who already walked in.
Exploitation attempts were seen on the very day the fix shipped. If an attacker reached your server before you updated, the patch won’t remove anything they left behind.
Self-check
Am I affected? Find out in 10 seconds.
Type the PHP version your website runs, or pick one below.
Turn on JavaScript to use the instant check, or find your version in the status table.
Your result will appear here.
Runs in your browser. Nothing you type is sent anywhere.
How do I find my PHP version?
- WordPress: Tools → Site Health → Info → Server.
- Hosting control panel: look for “PHP version” or “PHP settings”.
- Developers: check
phpinfo()on the web server. Command-linephp -vcan report a different version from the one your website uses. - Still unsure? Email us your website address and we’ll help you find out.
How ALIANDO protects you
Contain today. Verify this week. Modernize for good.
Six services, one accountable team. Start where your risk is highest; we’ll take it from there.
- Contain · Today
Emergency Patch & Harden
We find every PHP instance you run (production, staging, containers, forgotten microsites), apply the fixed releases, restart every worker and isolate whatever can’t be patched yet.
Request emergency help - Verify · This week
Compromise Assessment
Patched isn’t the same as clean. We hunt for web shells, rogue scheduled tasks, unknown accounts and suspicious outbound connections, then tell you plainly whether anyone got in.
Ask about an assessment - Verify · This week
Penetration Testing
Our ethical hackers attack your websites, APIs and servers the way real criminals would, then hand you a prioritized, plain-language list of what to fix first.
Plan a pentest - Modernize · This quarter
PHP Transition Consultancy
Upgrade to PHP 8.4 or 8.5, or move to another platform? We assess your code, team and roadmap, then give you an objective plan with costs, risks and timeline.
Talk to a consultant - Modernize · This quarter
Website Redevelopment
We rebuild legacy PHP 5 and 7 sites on a modern, supported stack: secure by design, faster, easier to maintain, and hosted on managed Azure if you choose.
Discuss a rebuild - Protect · Always on
24x7 SOC & Managed XDR
Our 24x7 Security Operations Center watches for attacks and responds around the clock, so the next critical flaw doesn’t wait for Monday morning.
Get 24x7 coverage
Why ALIANDO
Good People. Great Professionals.
When a critical flaw lands, you want people who have done this before. ALIANDO secures, runs and modernizes critical platforms for organizations around the world.
- 1000+organizations served in 32 countries
- 340+specialists worldwide
- 24x7Security Operations Center
- Azure Expert MSPMicrosoft endorsement earned through annual audits
What happens next
Three steps to knowing where you stand
1. Send one email
Tell us your website and, if you know it, your PHP version. It takes two minutes.
2. Have a 30-minute triage call
A security specialist reviews your exposure with you and answers your questions, with no obligation.
3. Get your action plan
Clear priorities: what to contain now, what to verify and how to modernize.
FAQ
Questions we’re hearing this week
Our hosting provider manages PHP. Are we safe?
Not automatically. Ask your provider which PHP version your site runs and when it was last updated. More than a third of PHP websites still run PHP 7 or older, versions with no official fix, and a provider’s patch can’t tell you whether someone got in before it was applied.
We use WordPress, Drupal or Laravel. Does this affect us?
Yes, if your server runs an unpatched PHP version. The flaws are in PHP itself, so updating your CMS, plugins or framework won’t close them. Only updating PHP does.
Can’t we just change a PHP setting instead?
Only as a stopgap. Even the PHP project itself says there is no complete workaround: updating is the only safe choice. Configuration tweaks block some known attack paths, not all of them.
We’ve already patched. Are we done?
Almost. Confirm that every PHP worker was restarted, because the fix only takes effect after a restart. Then check for signs of a break-in from before you patched: web shells, unexpected scheduled tasks or new accounts. And if you run PHP 8.2, plan your upgrade now: its security support ends on 31 December 2026.
Should we move away from PHP altogether?
Not necessarily. PHP 8.4 and 8.5 receive security fixes until the end of 2028 and 2029. The right answer depends on your codebase, your team and your roadmap. Our transition consultancy gives you an objective recommendation, not a sales pitch.
Act now
The patch is out. Attackers are already looking for servers that skipped it.
Every day an unpatched server stays online is another day for someone else to get in first. Let’s close the door, and make sure no one is already inside.
Include your website address and PHP version if you know them. No obligation.
ALIANDO is not affiliated with the PHP project.
Running PHP?Check your exposure today.
Get help now