No. CVE-2026-60137
Hackers can inject database commands into WordPress sites
Yes. Attackers are using this right now.
Anyone with a WordPress website, including small business sites.
What to do
Update WordPress to the latest version. Check: Dashboard > Updates.
Attack likelihood is EPSS, a daily estimate from FIRST.org of how likely this bug is to be used in attacks in the next 30 days.
The official description
WordPress Core contains a SQL injection vulnerability when a plugin or theme passes untrusted input to the parameter. This vulnerability can be chained with CVE-2026-63030 to allow an unauthenticated attacker to gain remote code execution on default WordPress installations.
For your tech helper or AI assistant
A read-only checklist. Paste it into Claude, ChatGPT or a coding agent; it only looks and changes nothing.
Read-only check, change nothing, send nothing anywhere.
Is WordPress Core (CVE-2026-60137) installed or running on this machine or in this project?
1. Find every copy and its version (apps, packages, containers, lockfiles).
2. Compare each version against the vendor's fixed version for CVE-2026-60137. Quote the vendor page you used.
3. Report a table: where, version, fixed version, status (exposed / fixed / not installed / unsure).
4. List the exact update steps, but do not run them.Code on GitHub
Repos named after this bug. Some are scanners or write-ups, some are working attack code. Do not run them on a machine you care about.
- MRdark-ops/WP2Shell--CVE-2026-63030-CVE-2026-60137- · 2 stars
- AdarshThakur14777-cyber/CVE-2026-60137 · 0 stars
- northsia/CVE-2026-60137-With-Skip-SSL · 0 stars