Critical WordPress Core Vulnerability: What You Need to Know
On July 17, 2026, the WordPress Security Team released urgent security updates addressing a critical vulnerability chain that could allow unauthenticated attackers to take complete control of vulnerable websites. This is not a plugin vulnerability that affects a subset of sites; this flaw exists in WordPress core itself, meaning even a fresh installation with no plugins is exploitable.
Here is what every WordPress site owner needs to know and the actions you must take immediately.
Understanding the Threat: A Two-Vulnerability Chain
The WordPress Security Team patched two security vulnerabilities that, when chained together, create a devastating attack vector.
CVE-2026-60137: Unauthenticated SQL Injection
The first vulnerability is an unauthenticated SQL injection flaw affecting WordPress versions 6.8 through 7.0.1. It exists in the author__not_in parameter of WP_Query, where insufficient escaping and inadequate query preparation allow attackers to append malicious SQL queries. This vulnerability carries a CVSS score of 7.5 (High).
CVE-2026-63030: Remote Code Execution (wp2shell)
The second vulnerability enables unauthenticated remote code execution (RCE) via the WordPress REST API batch request endpoint (/wp-json/batch/v1). This flaw, dubbed wp2shell, involves a route validation desynchronization that allows a validated sub-request to be dispatched to an unintended callback. When chained with SQL injection, an attacker can execute arbitrary code on the server. This vulnerability carries a CVSS score of 9.8 (Critical).
The combination means an attacker can:
- Execute code on your server with no authentication required
- Upload and activate malicious plugins
- Gain complete control of your website and its underlying data
- Potentially use your site to launch further attacks
Who Is Affected?
| Branch | Affected Versions | Patched Version |
|---|---|---|
| 6.8.x | 6.8.0 through 6.8.5 | 6.8.6 |
| 6.9.x | 6.9.0 through 6.9.4 | 6.9.5 |
| 7.0.x | 7.0.0 through 7.0.1 | 7.0.2 |
WordPress 6.9 was released on December 2, 2025, meaning every affected site is running a release less than eight months old. Sites on versions earlier than 6.9 are not affected by CVE-2026-63030, though they may still be vulnerable to CVE-2026-60137.
The Urgency: Why You Must Act Now
This vulnerability is exceptionally dangerous for several reasons:
No Authentication Required: Attackers do not need a valid account or any user interaction. An anonymous HTTP request can trigger the exploit against a default WordPress installation.
No Plugins Required: The vulnerable code exists in WordPress core. Even a fresh installation with zero plugins is exploitable.
Widespread Exposure: Over 500 million websites run WordPress. While not all are vulnerable, the potential attack surface is massive.
Public Proof-of-Concept Likely Imminent: Given that WordPress is an open-source project and AI models can analyse source code, security researchers believe a public proof-of-concept will be made available in a very short period of time.
What You Must Do Now
1. Update Immediately
The WordPress Security Team has released patched versions: 6.8.6, 6.9.5, and 7.0.2.
To update:
- Log in to your WordPress dashboard
- Navigate to Dashboard → Updates
- Click “Update Now”
The WordPress team has initiated automatic updates for sites with auto-updates enabled. However, do not assume your site has been updated. Verify manually.
2. Verify Your WordPress Version
Even if you believe automatic updates are enabled, check your actual version:
- In your WordPress dashboard, look at the bottom right corner
- Or navigate to Tools → Site Health → Info
3. If You Cannot Update Immediately
Searchlight Cyber has proposed temporary mitigations, but these are stopgaps and should not replace updating:
- Block both
/wp-json/batch/v1andrest_route=/batch/v1at your Web Application Firewall (WAF) - Deploy a short drop-in plugin that rejects anonymous
/batch/v1requests
Warning: These mitigations can break legitimate integrations. They are not a substitute for patching.
How BG Cyber Connect Can Help
At BG Cyber Connect, we understand that keeping your WordPress site secure requires constant vigilance. Our team can:
Perform an Immediate Security Audit
We will verify your WordPress version, confirm whether you are patched, and identify any other vulnerabilities in your installation.
Implement Proactive Security Monitoring
We deploy Web Application Firewalls (WAFs) and monitoring tools that can block exploit attempts before they reach your site.
Provide Ongoing Patch Management
We monitor security advisories and ensure your site is updated promptly when critical patches are released.
Remediate Compromised Sites
If your site has already been compromised, we can help you clean it, restore clean backups, and harden your security posture.
The Bottom Line
A critical vulnerability chain in WordPress core allows unauthenticated attackers to execute code and take complete control of vulnerable sites. The patches are available, but you must act now. Do not assume automatic updates have protected you. Verify your version, update if necessary, and consider implementing professional security monitoring.
Your website is your business. Don’t leave it vulnerable.
Need Help Securing Your WordPress Site?
Contact BG Cyber Connect for an Immediate Security Assessment
Explore our comprehensive WordPress security services:
BGCC Cybersecurity Solutions


