WordPress: RCE vulnerability

WordPress

Threat actors are attempting to exploit a high-severity unauthenticated race condition leading to remote code execution in WordPress

Do this now

Restrict public access to the affected WordPress site and watch for the vendor fix before re-enabling it.

First seen: 30 Oct 2026
Last update: 30 Oct 2026, 12:19 UTC
Source: news
On the menu as: WordPress

Check this repository for exposure to one security incident from pwned.coffee. Report first, change nothing until I say so.

## WordPress: RCE vulnerability
Severity: unknown. Patch status: no fix yet.
Affected: WordPress

Threat actors are attempting to exploit a high-severity unauthenticated race condition leading to remote code execution in WordPress

## Steps
1. Search the repo, its CI and infra config for WordPress. If present, report the version in use and whether it's affected.
2. There is no fix yet. Until one ships: restrict network access to it.

## Report
A table: file, product or package, version in use, affected yes/no, exact fix. Then anything a human has to check outside the repo.

If you have the pwned.coffee MCP server (https://pwned.coffee/mcp), call lookup_cve for the latest, and check_repo with this repo's lockfiles, Dockerfiles and workflows for a full receipt.
Sources: https://www.securityweek.com/fresh-wordpress-vulnerability-in-attackers-crosshairs/
https://pwned.coffee/i/wordpress-rce-vulnerability

Receipt

Exploitation: No known exploitation
Score: No CVSS published yet: severity unknown.
Last checked: 30 Oct 2026, 13:19 UTC

Sources: KEV – CVE record – Vendor –

Sources

securityweek.com: Fresh WordPress Vulnerability in Attackers’ Crosshairs

Wrong fix version, or a source we missed? Send it back to chef@pwned.coffee with the source, and we'll correct it here.

Totalone coffee