Wordfence says one of the PHP flaws from this week can run attacker code on a WordPress server. Its Threat Response team confirmed unauthenticated code execution in an isolated lab. The flaw is CVE-2026-129289, a PHP-FPM bug rated 9.2 out of 10.
PHP-FPM is the part of your server that runs PHP code. We covered the wider PHP release yesterday.
What Wordfence found
An attacker with no login may be able to make PHP run a request that never passed through the web server’s normal checks. If it works, the attacker runs PHP code with the permissions of your site’s PHP process.
This is a flaw in PHP, not in WordPress core, a plugin, or a theme. WordPress’s normal REST API handling supplies one of the behaviors the attack needs. Updating WordPress will not fix it.
Who is exposed
Not every site is. The demonstrated attack needs two things:
- A vulnerable PHP version.
- A web server that reuses its private connections to PHP-FPM.
Wordfence says standard NGINX setups do not turn that reuse on by default. In its lab, the same test ran no code after PHP was updated. It also failed once connection reuse was turned off.
What to do
Ask your host which PHP version you run. The fixed releases are 8.2.36, 8.3.37, 8.4.28, and 8.5.13. Some hosts ship fixes under different package numbers, so ask whether the patch is applied rather than relying on the number alone.
If you manage your own server and cannot update yet, turn off connection reuse between the web server and PHP-FPM. Restart PHP after any change.
End of article