PHP2Shell, Split Fee and Your Agency Website
The security story of the week is PHP2Shell, a pair of critical flaws in PHP, the programming language WordPress is written in. The short answer for Split Fee customers: none of Split Fee’s own systems run PHP, so PHP2Shell has nothing to reach, and there is nothing you need to do on your account.
Your agency’s own website is worth a quick check, though, so further down is a set of questions for your web host or developer.
What PHP2Shell is
PHP2Shell is two flaws in the core of PHP: CVE-2026-109618 and CVE-2026-109619. (A CVE is the public reference number a disclosed flaw is given.) The PHP security team rates each one 9.2 out of 10 on CVSS v4, the usual severity scale.
Both allow unauthenticated remote code execution: someone who has never logged in can make the web server run code of their choosing. Researchers have traced the affected code back to PHP 5.4, so every release line from 5.4 to 8.5 is exposed until it is updated.
News of the flaws leaked online the day before the fixes came out, and attacks have already started. Cloudflare reports early attacks, and watchTowr reports exploitation attempts against both flaws.
PHP released fixed versions on 21 October: 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Versions 8.1 and older are end of life, meaning the PHP project no longer maintains them. Even so, 7.4, 8.0 and 8.1 get the fix as source code, though not as an official release. Anything from 5.4 to 7.3 gets no fix from the PHP project at all. Temporary settings changes reduce exposure, but the PHP team is clear that updating is the only complete fix (CERT-EU’s advisory sets out the detail).
Where Split Fee stands
No part of Split Fee’s own systems runs PHP. The app, the services behind it and this website are built on other technology, and our servers run on AWS in London. PHP2Shell has nothing on our side to reach.
No password reset, no reconnecting anything. A few things were already in place before this week:
- The web firewall in front of the app turns away requests that probe for PHP files.
- Every change to the app is scanned for components with known security flaws before it can be deployed.
- Automated update requests keep those components current.
How Split Fee looks after candidate data is unchanged too. Candidate and client names stay hidden until both agencies have signed the placement, every reveal is logged, and the platform is built for UK GDPR. How it works covers each step, and sharing candidates under UK GDPR explains why names are held back so long.
Two more in the news this week
Palo Alto Networks’ Unit 42 research team reported this week that ransomware groups are now exploiting CVE-2026-0257 in PAN-OS GlobalProtect, the remote access part of its firewalls. Attacks on that flaw have been reported since May. Separately, a public proof of concept (working attack code anyone can download) is now out for Fortinet FortiSIEM CVE-2026-106173.
The Split Fee platform uses no Palo Alto Networks or Fortinet equipment, so neither flaw touches it. If your firewall, VPN or security monitoring comes from either vendor, give whoever looks after your IT a call today.
Five questions for your web host this week
Many agency websites, job boards and candidate portals are built on WordPress, and WordPress runs on PHP. The flaw sits in PHP rather than in WordPress, so updating WordPress and its plugins does not fix it on its own. What counts is the PHP version on the server.
If a host or developer looks after the server for you, these questions get a clear answer quickly:
- Which version of PHP does our site run on? You are looking for 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or later in the same line. Hosts that use their operating system’s PHP packages can show an older number with the fix already in, so ask them to confirm.
- If it is 8.1 or older, what is the plan? Ask how the fix will reach you, and when you will move to a supported version.
- Have temporary protections gone on while the update is scheduled?
- Does this cover everything with our name on it? That includes the job board, any candidate portal or application form, and landing pages or older microsites hosted somewhere else. Anything that collects CVs comes first, because that is candidate data.
- Who do we call if something looks wrong? Get a name and a direct number now.
None of this means touching a server yourself. A short email is enough to start.
The short version
PHP2Shell, the PAN-OS flaw and the FortiSIEM flaw do not reach Split Fee’s own systems, and there is nothing to do on your account. Your own website deserves that email this week.
If you have a question about your account, ask Chloë in the app, and she can raise a ticket with the team when you need a person. New to Split Fee? See how it works for agencies.
This article is general information, not security advice. For your own website and systems, speak to your web host, your IT provider or a security professional, or start with the National Cyber Security Centre’s guide for small organisations.
What to read next
- Sharing Candidates Between Agencies Under GDPR. Why names stay hidden for so long.
- How Split Fee Works. A split placement, step by step.
- Meet Chloë, Split Fee’s New AI Support Assistant. Answers in the app, with a person behind her.
Got a role or a candidate to share?
Split Fee matches it with agencies across the UK, and you split the fee when you place together.