WordPress 7.0.2 wp2shell

What to do

• Check whether you use Pantheon Global CDN. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1d 2h it lasted.

  Anything that failed between 2026-07-20 19:26 UTC and 2026-07-21 21:33 UTC may need a replay.

• Subscribe to Pantheon's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=pantheon works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Pantheon 5

1. monitoringJul 20, 2026, 7:26 PM UTC

   Summary On July 17, 2026, the WordPress security team disclosed two chained vulnerabilities in WordPress core, publicly referred to as "wp2shell": - CVE-2026-60137 — a SQL injection issue in WordPress core (WP_Query / author__not_in). - CVE-2026-63030 — a REST API batch-route confusion issue which, chained with the above, can lead to unauthenticated remote code execution. Who is affected This affects specific versions of WordPress core: - 6.9.x — affected by both issues (RCE-capable). Patched in 6.9.6. - 7.0.x — affected by both issues (RCE-capable). Patched in 7.0.2. - 6.8.x — affected by the SQL injection issue only (not the full RCE chain). Patched in 6.8.6. Sites already on 6.8.6 / 6.9.6 / 7.0.2 or later, or on versions prior to 6.8, are not affected by this chain. Why it matters Chained together, these vulnerabilities can allow an unauthenticated attacker to execute code against a vulnerable site. Pantheon’s immutable containers prevent the deployment of webshells, bitcoin miners, or other exploits that leverage a downloaded payload in production environments. However, SQL Injection can still be used to deface or hijack sites. Because working exploits are publicly available, we expect attack volume to rise. What you should do — action required Update WordPress core to a patched version as soon as possible — 7.0.2, 6.9.6, or 6.8.6 depending on your branch — from your Pantheon Dashboard or via Terminus. Updating core is the definitive fix. See the WordPress 7.0.2 Security Release note: https://docs.pantheon.io/release-notes/2026/07/wordpress-7-0-2 What Pantheon is doing - We are actively monitoring platform traffic for exploitation attempts targeting the affected REST API endpoint. - We have observed sites being probed for vulnerability and have actively mitigated against sources of scripted activity already. - We are deploying targeted mitigations at the network level to programmatically prevent exploit attacks across the platform and can confirm that released exploit code is being mitigated. - Will update this post with more information as those efforts progress.

   provider

2. monitoringJul 20, 2026, 10:20 PM UTC

   We can observe our mitigations denying an increasing volume of requests and are continuing to gather data to enhance our response. We will provide an update Tuesday morning.

   provider

3. monitoringJul 21, 2026, 1:43 PM UTC

   We are continuing to monitor traffic patterns and adapt network-level mitigations in response.

   provider

4. monitoringJul 21, 2026, 9:33 PM UTC

   Network mitigations are now active and successfully blocking exploit attempts against vulnerable API endpoints without affecting normal site operations. Continuous monitoring is in place. This platform-level mitigation is a safeguard, not a permanent fix for your application. To fully secure your environment, update WordPress core immediately as detailed in the Pantheon Documentation: https://docs.pantheon.io/core-updates

   provider

5. resolvedJul 21, 2026, 9:33 PM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.