Subscribe to Newsletter
Enter your email address below and subscribe to our newsletter

The wp2shell and CVE-2026-60137 vulnerabilities can allow remote code execution on WordPress websites. Learn how the attack works and how to protect your website.
The German Federal Office for Information Security (BSI) is warning of two vulnerabilities in WordPress that, in combination, allow unauthenticated remote code execution (RCE). The chain of vulnerabilities was described as... „"wp2shell"“ designated and has a CVSS score of 9,8 / 10 Proof-of-concepts are publicly available, and initial exploits have already been reported. Affected operators must immediately Act. Criticality: 3 / OrangeTLP: CLEAR CVE-2026-60137 · CVE-2026-63030
BITS-H No. 2026-271984-1132 · Version 1.1 · July 20, 2026
The following summary provides a structured overview of all relevant key data from this security advisory – from the affected versions to the resolving updates. All information is taken from the official BSI report BITS-H No. 2026-271984-1132.
Versions older than 6.8 are not affected.
Active exploitation has been confirmed. Proof-of-concepts are publicly available. Exploitation requires no authentication.
Install patch + set up workaround (WAF)
On July 17, 2026, WordPress released a security update that fixed two vulnerabilities in its core system. Combined, these vulnerabilities allowed an unauthenticated attacker to execute arbitrary code on the affected server – without any authentication. Security researchers described the chain of vulnerabilities as „"wp2shell"“ designated.
Faulty sanitization of the parameter author__not_in in WP_Query queries. Enables SQL injection attacks, allowing attackers to read database contents – including password hashes of the table. wp_users.
A vulnerability in the WordPress REST API, in combination with CVE-2026-60137, allows full remote code execution without authentication. The attack exploits the batch endpoint. /wp-json/batch/v1.
The company Searchlight Cyber discovered the vulnerability using OpenAI GPT-5.6 Sol Ultra. Technical details and the AI prompts used were published on the company blog. A proof of concept was published on GitHub.
The BSI classifies the chain of vulnerabilities as very critical The existence of public proof-of-concepts and the ease of exploitation without authentication massively increase the risk. Just a few hours after the patches were released, the first proofs of concept were circulating on the internet – a clear indication of the reduced time-to-exploit.
Combined score of the wp2shell vulnerability chain (CVSS 3.1)
No registration required – attacks are possible completely anonymously
Two vulnerabilities together form the critical attack chain.
Public exploits were available just hours after the patch was released.
WordPress operators whose systems were not automatically updated on the day of release (July 17, 2026) should immediately check them for any existing compromise.
Not all WordPress versions are affected to the same extent. The following overview shows which versions are affected by which vulnerability and which update version closes the gap. Administrators should first check which version is running on their system.
| version | Affected by | Fixing version | urgency |
| WordPress 6.8.0 – 6.8.5 | CVE-2026-60137 (only) | 6.8.6 | High |
| WordPress 6.9.0 – 6.9.4 | CVE-2026-60137 + CVE-2026-63030 | 6.9.5 | Critical |
| WordPress 7.0.0 – 7.0.1 | CVE-2026-60137 + CVE-2026-63030 | 7.0.2 | Critical |
| WordPress 7.1 beta | CVE-2026-60137 + CVE-2026-63030 | 7.1 beta2 | Critical |
| WordPress < 6.8 | Not affected | – | – |
The limited version range affected, as well as the automatic updates enabled by default, reduce the likelihood of a very widespread attack wave. Nevertheless, vulnerable WordPress instances can still become targets of automated attacks in the short and medium term.
The BSI recommends, immediately to install one of the secured versions. For operators who have disabled automatic updates or for whom they do not work (e.g., due to file permissions), a manual installation absolutely necessary.
Enable automatic updates or manually update to version 6.8.6 / 6.9.5 / 7.0.2 / 7.1 beta2. Create a backup beforehand.
Setting up a Web Application Firewall and accessing it /wp-json/batch/v1 as well as parameters ?rest_route=/batch/v1 block.
Install a plugin to block anonymous access to the WordPress REST API to prevent attacks without authentication.
Use the Searchlight Cyber website checker at wp2shell.com Test whether your own installation is affected.
Since initial exploits have already been reported, all operators – especially those without automatic updates on July 17, 2026 – should examine their systems for signs of compromise. The following checklist is based on current recommendations from security experts.
/wp-json/batch/v1 – Increased inquiry numbers are suspicious?rest_route=/batch/v1wp2_* or w2s_*@wp2shell.invalid or @wp2shell.shellcode.loloembed_cache and customize_changesetIn case of suspected compromise: Immediately isolate the system, initiate evidence preservation, terminate all active sessions, and reset all user passwords. Password hashes may have been extracted via SQL injection and cracked offline.
In the event of an actual or suspected compromise, all affected login credentials must be changed immediately. The SQL injection vulnerability allows attackers access to all password hashes of the wp_users-tables that can then be cracked offline.
Change the password for your WordPress user account with administrator privileges immediately. Use a strong, unique password.
Change the passwords of all email accounts linked to the WordPress instance, especially admin email addresses.
Reset all API keys, tokens and access data for plugins and extensions (e.g., online shop, payment services, CDN).
Passwords that have also been used for other services must also be changed with the respective providers.
Beyond immediate protective measures, the BSI recommends long-term measures to permanently harden WordPress installations against similar attacks and to improve responsiveness to future security incidents.
Check if automatic updates are enabled and functioning correctly. If updates are disabled, establish a process that installs new security updates promptly.
Operators of important websites should generally use a WAF to defend against attacks in the short term – even in the case of as yet unknown vulnerabilities (zero-day).
Regularly analyze log files and system activity. Identify unusual patterns such as frequent API calls or new admin accounts early on.
Ensure regular, separately stored backups and have an incident response plan in place for the event of a compromise.
Daily updates:Information service of CERT-Bund
This document is as TLP:CLEAR It is classified and may be distributed without restrictions – apart from copyright aspects.
Documents rated TLP (except CLEAR) must not be uploaded to third-party platforms (VirusTotal, translation services, etc.).
Version history: 1.0 – 18.07.2026 | 1.1 – 20.07.2026 (Update with PoC reports and expanded compromise indicators)