Attackers began exploiting a WordPress attack chain known as wp2shell within hours of public exploit code appearing around 17-18 July 2026. The chain lets an attacker run their own code on a site without logging in. Reports describe mass scanning of WordPress sites, followed by the installation of malicious plugins and web shells.
What is going on
wp2shell is not one flaw but two bugs used together. The first, CVE-2026-60137, is an SQL injection issue, meaning an attacker can push their own commands into the site's database queries. The second, CVE-2026-63030, is a code execution bug in the WordPress REST API, the interface other software uses to talk to your site.
Used in sequence, they give unauthenticated remote code execution. In plain terms: a stranger can make your website run their instructions, with no password needed.
Think of it as someone using a gap in the mailroom to get a key cut for the front door. Once inside, attackers drop a web shell, a small file that acts as a permanent back door for sending further commands.
Who is affected
The issue affects WordPress core, not a single plugin. Vulnerable versions are 6.9.0 through 6.9.4, and 7.0.0 through 7.0.1.
Fixes are available in 7.0.2, 6.9.5 and 6.8.6. Any public WordPress site on an affected version is a target, because the scanning is automated and does not pick by size or industry.
What to do now
- Check your version and update. In the WordPress dashboard, open Updates and confirm you are on 7.0.2, 6.9.5 or 6.8.6, or later.
- Review your plugins. Remove anything you did not install yourself, especially plugins with odd names or no description.
- Look for unexpected PHP files. Ask your host or developer to check the uploads folder and theme folders for
.phpfiles that should not be there. - Check admin accounts. Under Users, delete any administrator account you do not recognise, and reset passwords for the ones you keep.
- If you find signs of a break-in, restore from a clean backup taken before mid-July 2026, then update before putting the site back online.
Updating alone does not remove a back door that is already in place. That is why the file and account checks matter even after you patch.
How to check your own site
Scantinel's free Website Security Check reports outdated CMS versions, known-vulnerable plugins, missing security headers, weak TLS and email-authentication gaps, so you can see at a glance whether your WordPress version is still exposed. For a deeper look, you can run a full scan, which adds WordPress deep scans, exposed-file and secret checks, and port and service checks with CVE matching, on sites whose ownership you have verified.
Source: BleepingComputer, July 2026.
Comments
No comments yet.