Loading story…
COLCERT issued alert 20260928-120 warning of exploitation associated with Kapibala_wp2shell_WordPress. Reporting identifies the alleged issue as CVE-2026-63030, a potential remote-code-execution path in WordPress core that requires no vulnerable plugin and targets the REST API batch endpoint at /wp-json/batch/v1/.
The reported technique uses malformed URLs to desynchronize batch-request validation from the callbacks selected for execution, potentially allowing a callback to execute after validation fails. Organizations running WordPress should urgently determine whether their deployments expose the batch REST endpoint, review web and application logs for anomalous requests to /wp-json/batch/v1/, and watch for unauthorized files or web shells in WordPress web roots; the available notices do not specify affected versions, confirmed indicators, or an official remediation.
See which actors are running it and whether you're in range.
3 events from the most recent confirmed update back to the earliest known activity.
COLCERT AL published alert 20260928-120 concerning exploitation identified as “Kapibala_wp2shell_WordPress.” The supplied notice associates the activity with WordPress but provides no CVE, affected versions, indicators, attribution, or mitigation details.
A campaign active from June through September 2026 was attributed by CSIRT Panamá to Red Heron, which allegedly exploited WordPress flaws including CVE-2026-63030 and CVE-2026-60137 to compromise a Western government organization and exfiltrate more than 18,566 records. The report also documented exploitation of ZyXEL GS1900 switches and other exposed platforms, affecting 49 WordPress organizations in 29 countries and 996 ZyXEL devices in 48 countries.
An article described “wp2shell” as a plugin-free WordPress exploitation technique allegedly targeting CVE-2026-63030 in REST API batch processing at the /wp-json/batch/v1/ endpoint. It claimed malformed URLs could desynchronize validation and callback-selection arrays, allowing execution of a callback associated with another request.
Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.
Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
Correlate live exploitation activity against the software you actually run, and see where you're exposed.
3 references tracked. Mallory keeps watching after this page renders.
xakep.ru
Open sourcecolcert.gov.co
Open sourcecert.pa
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
WordPress released security updates for two core vulnerabilities, **CVE-2026-63030** and **CVE-2026-60137**, that can be chained to make a blind SQL injection remotely reachable without authentication and, in some cases, lead to **remote code execution**. The issue, dubbed **`wp2shell`**, stems from REST API batch-route confusion in the `/wp-json/batch/v1` endpoint combined with SQL injection, affecting WordPress versions **6.9.0 through 6.9.4** and **7.0.0 through 7.0.1**. Researchers said the route-confusion flaw carries a **CVSS 9.8** rating, while the second SQL injection bug is rated **CVSS 5.9**. WordPress fixed the flaws in **6.9.5** and **7.0.2**, and also backported the SQL injection fix to **6.8.6**. The vulnerabilities were reported by Adam Kues of Assetnote through the WordPress HackerOne program, and while exploitation had not been confirmed at the time of disclosure, a public proof of concept later became available, increasing the risk of rapid weaponization. Administrators were urged to verify that forced automatic updates succeeded and, if immediate patching was not possible, to apply mitigations such as blocking the REST batch endpoint with a WAF.
Jul 31, 2026
WordPress released **7.0.2** to fix two core vulnerabilities that can be chained into unauthenticated remote code execution, including **CVE-2026-63030** and **CVE-2026-60137**. The flaws affect default WordPress installations without plugins, with the RCE path impacting **6.9.0 through 6.9.4**, **7.0.0 through 7.0.1**, and **7.1 beta**, while the SQL injection issue also affects the **6.8** branch. WordPress issued backported fixes in **6.9.5**, **6.8.6**, and **7.1 Beta 2**, enabled forced auto-updates for affected sites, and said the attack chain abuses the REST API batch endpoint to trigger route confusion, bypass request handling restrictions, and reach SQL injection that can lead to full site compromise. Security vendors moved quickly to contain exposure as public technical details began to emerge. Cloudflare deployed WAF protections for both CVEs for all customers and Wordfence added firewall coverage for premium users, but both stressed that filtering is only a temporary mitigation and that patching is the primary remediation. Researchers attributed the discovery to Adam Kues of Searchlight Cyber's Assetnote team, and while early reporting said no in-the-wild exploitation had been confirmed, a public GitHub proof of concept later demonstrated unauthenticated access to the vulnerable batch endpoint and blind SQL injection against affected versions, increasing the likelihood of rapid attacker weaponization.
Aug 26, 2026
CISA added four vulnerabilities to its Known Exploited Vulnerabilities catalog after confirming active exploitation, including two **WordPress Core** flaws that can be chained from SQL injection to unauthenticated remote code execution, the critical **Langflow** RCE `CVE-2026-0770`, and **DD-WRT** flaw `CVE-2021-27137`. The WordPress issues, `CVE-2026-60137` and `CVE-2026-63030`, affect default installations and have drawn warnings from CERT-FR and NCSC-NL because public proof-of-concept code is available and broader exploitation is considered likely or imminent. `CVE-2026-60137` stems from improper sanitization of the `author__not_in` parameter in `WP_Query` when plugins or themes pass untrusted input, affecting WordPress `6.8.x` before `6.8.6`, `6.9.x` before `6.9.5`, and `7.0.x` before `7.0.2`. Organizations were urged to prioritize patching those versions, update Langflow, and upgrade DD-WRT builds older than `45724`; where immediate WordPress patching is not possible, defenders were advised to restrict unauthenticated access to the REST batch API endpoint, including paths such as `/wp-json/batch/v1` or requests containing `rest_route=/batch/v1`.
Jul 25, 2026