WordPress vulnerabilitiesAnd the versions its exploited flaws hit.
WordPress is made by WordPress. We track 578 published vulnerabilities listed under that exact name, across 722 versions. 3 of them are on the list of flaws known to be exploited, the newest added on 21 July 2026. WordPress lists newer releases under their own names, such as Wordpress Mu, so check those pages too.
The most recent WordPress flaw added to the known-exploited list is CVE-2026-60137, on 21 July 2026. We keep watching the known-exploited list.
Is WordPress listed under other names? Yes.
WordPress also lists WordPress under more specific names, such as Wordpress Mu. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which versions of WordPress do the exploited flaws hit?
Each exploited flaw lists the versions it affects, usually as ranges. "6.8 to before 6.8.6" means from 6.8 up to, but not including, 6.8.6. Find your version, then patch.
- CVE-2026-60137Exploited list, 21 Jul 2026
WordPress Core SQL Injection Vulnerability
6.8 to before 6.8.66.9 to before 6.9.57.0 to before 7.0.2 - CVE-2026-63030Exploited list, 21 Jul 2026
WordPress Core Interpretation Conflict Vulnerability
6.9 to before 6.9.57.0 to before 7.0.2 - CVE-2016-10033Exploited list, 7 Jul 2025
PHPMailer Command Injection Vulnerability
up to 4.7
Which WordPress vulnerabilities are being exploited?
3 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 5.9WordPress Core SQL Injection Vulnerability
WordPress Core contains a SQL injection vulnerability when a plugin or theme passes untrusted input to the parameter.
- 9.8WordPress Core Interpretation Conflict Vulnerability
WordPress Core contains an interpretation conflict vulnerability that could allow an attacker to perform SQL Injection and achieve Remote Code Execution.
- 9.8PHPMailer Command Injection Vulnerability
PHPMailer contains a command injection vulnerability because it fails to sanitize user-supplied input.
Which WordPress flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- >99%
The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra parameters to the mail command and consequently execute arbitrary code via a \" (backslash double...
- 98%CVE-2022-21661High
WordPress is a free and open-source content management system written in PHP and paired with a MariaDB database.
- 98%CVE-2016-10045Critical
The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail command and consequently execute arbitrary code by leveraging improper interaction between the...
- 92%CVE-2019-8943Medium
WordPress through 5.0.3 allows Path Traversal in wp_crop_image().
- 87%CVE-2017-5487Medium
wp-includes/rest-api/endpoints/class-wp-rest-users-controller.php in the REST API implementation in WordPress 4.7 before 4.7.1 does not properly restrict listings of post authors, which allows remote attackers to...
- 86%CVE-2021-29447Medium
Wordpress is an open source CMS. A user with the ability to upload files (like an Author) can exploit an XML parsing issue in the Media Library leading to XXE attacks.
- 85%CVE-2009-2335Medium
WordPress and WordPress MU before 2.8.1 exhibit different behavior for a failed login attempt depending on whether the user account exists, which allows remote attackers to enumerate valid usernames.
- 85%CVE-2017-1001000High
The register_routes function in wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php in the REST API in WordPress 4.7.x before 4.7.2 does not require an integer identifier, which allows remote attackers...
- 83%CVE-2019-8942High
WordPress before 4.9.9 and 5.x before 5.0.1 allows remote code execution because an _wp_attached_file Post Meta entry can be changed to an arbitrary string, such as one ending with a .jpg?file.php substring.
- 83%CVE-2014-9034Medium
wp-includes/class-phpass.php in WordPress before 3.7.5, 3.8.x before 3.8.5, 3.9.x before 3.9.3, and 4.x before 4.0.1 allows remote attackers to cause a denial of service (CPU consumption) via a long password that is...
Running WordPress? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
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.
- Matched to
- WordPress on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 578 published vulnerabilities listed under the name WordPress, across 722 versions. The most recent WordPress flaw added to the known-exploited list is CVE-2026-60137, on 21 July 2026.
3 are on the list of flaws known to be exploited. The most recently added are CVE-2026-60137, CVE-2026-63030 and CVE-2016-10033.
WordPress also lists WordPress under more specific names, such as Wordpress Mu. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Each flaw names its own versions, usually as ranges. The newest, CVE-2026-60137, affects 6.8 to before 6.8.6, 6.9 to before 6.9.5, 7.0 to before 7.0.2. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track WordPress. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.