WordPress versions
WordPress: update to 7.1.5, 7.0.9, 6.9.12, 6.8.13, 6.7.12, 6.6.12 or the safe release of one of 19 more supported branches. 4.6 and older have reached end of life in the lifecycle data.
Data: .
Which WordPress branch to run
The newest safe release is the newest release of a branch that still gets fixes and that no CVE record we read names as affected. Records whose versions we cannot place on a branch are counted at the end of the page.
| Branch | Status | Newest safe release | Upgrade to |
|---|---|---|---|
| 7.12 CVE records that this page reads | Bug and security fixes, no end date announced | 7.1.5 | 7.1.5 (this branch) |
| 7.05 CVE records that this page reads | Security fixes only, no end date announced | 7.0.9 | 7.0.9 (this branch) |
| 6.95 CVE records that this page reads | Security fixes only, no end date announced | 6.9.12 | 6.9.12 (this branch) |
| 6.83 CVE records that this page reads | Security fixes only, no end date announced | 6.8.13 | 6.8.13 (this branch) |
| 6.72 CVE records that this page reads | Security fixes only, no end date announced | 6.7.12 | 6.7.12 (this branch) |
| 6.62 CVE records that this page reads | Security fixes only, no end date announced | 6.6.12 | 6.6.12 (this branch) |
| 6.54 CVE records that this page reads | Security fixes only, no end date announced | 6.5.15 | 6.5.15 (this branch) |
| 6.47 CVE records that this page reads | Security fixes only, no end date announced | 6.4.15 | 6.4.15 (this branch) |
| 6.36 CVE records that this page reads | Security fixes only, no end date announced | 6.3.15 | 6.3.15 (this branch) |
| 6.27 CVE records that this page reads | Security fixes only, no end date announced | 6.2.16 | 6.2.16 (this branch) |
| 6.17 CVE records that this page reads | Security fixes only, no end date announced | 6.1.17 | 6.1.17 (this branch) |
| 6.08 CVE records that this page reads | Security fixes only, no end date announced | 6.0.19 | 6.0.19 (this branch) |
| 5.97 CVE records that this page reads | Security fixes only, no end date announced | 5.9.21 | 5.9.21 (this branch) |
| 5.89 CVE records that this page reads | Security fixes only, no end date announced | 5.8.20 | 5.8.20 (this branch) |
| 5.76 CVE records that this page reads | Security fixes only, no end date announced | 5.7.22 | 5.7.22 (this branch) |
| 5.66 CVE records that this page reads | Security fixes only, no end date announced | 5.6.24 | 5.6.24 (this branch) |
| 5.56 CVE records that this page reads | Security fixes only, no end date announced | 5.5.25 | 5.5.25 (this branch) |
| 5.417 CVE records that this page reads | Security fixes only, no end date announced | 5.4.26 | 5.4.26 (this branch) |
| 5.317 CVE records that this page reads | Security fixes only, no end date announced | 5.3.28 | 5.3.28 (this branch) |
| 5.217 CVE records that this page reads | Security fixes only, no end date announced | 5.2.31 | 5.2.31 (this branch) |
| 5.116 CVE records that this page reads | Security fixes only, no end date announced | 5.1.29 | 5.1.29 (this branch) |
| 5.017 CVE records that this page reads | Security fixes only, no end date announced | 5.0.32 | 5.0.32 (this branch) |
| 4.917 CVE records that this page reads | Security fixes only, no end date announced | 4.9.36 | 4.9.36 (this branch) |
| 4.817 CVE records that this page reads | Security fixes only, no end date announced | 4.8.35 | 4.8.35 (this branch) |
| 4.717 CVE records that this page reads | Security fixes only, no end date announced | 4.7.40 | 4.7.40 (this branch) |
| 4.614 CVE records that this page reads | Ended on 31 July 2025 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 4.514 CVE records that this page reads | Ended on 31 July 2025 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 4.414 CVE records that this page reads | Ended on 31 July 2025 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 4.314 CVE records that this page reads | Ended on 31 July 2025 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 4.214 CVE records that this page reads | Ended on 31 July 2025 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 4.114 CVE records that this page reads | Ended on 31 July 2025 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 4.012 CVE records that this page reads | Ended on 1 December 2022 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 3.912 CVE records that this page reads | Ended on 1 December 2022 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 3.812 CVE records that this page reads | Ended on 1 December 2022 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 3.712 CVE records that this page reads | Ended on 1 December 2022 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 3.61 CVE record that this page reads | Ended on 24 October 2013 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 3.5 | Ended on 1 August 2013 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 3.4 | Ended on 11 December 2012 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 3.3 | Ended on 13 June 2012 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 3.2 | Ended on 12 December 2011 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 3.1 | Ended on 4 July 2011 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 3.0 | Ended on 23 February 2011 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 2.9 | Ended on 17 June 2010 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 2.8 | Ended on 18 December 2009 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 2.7 | Ended on 10 September 2009 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 2.6 | Ended on 10 December 2008 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 2.5 | Ended on 14 July 2008 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 2.3 | Ended on 29 March 2008 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 2.2 | Ended on 24 September 2007 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 2.1 | Ended on 24 September 2007 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 2.0 | Ended on 5 August 2007 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 1.5 | Ended on 26 December 2005 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 1.2 | Ended on 17 February 2005 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 1.0 | Ended on 22 May 2004 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 0.72 | Ended on 3 January 2004 | None, the branch has ended | 4.7.40 (move to 4.7) |
| 0.71 | Ended on 11 October 2003 | None, the branch has ended | 4.7.40 (move to 4.7) |
Exploited, or likely to be
CVE records for WordPress that CISA lists as exploited, that have a public exploit, or that EPSS rates 0.50 or more, with the releases that fix each where the record names them. 7 of the 10 records shown name one.
| Record | Signs of exploitation | Fixed in |
|---|---|---|
| CVE-2026-63030WordPress < 7.0.2 - REST API batch-route confusion and SQL injection issue leading to Remote Code Execution9.8 Critical · published 17 July 2026 | On CISA's list Metasploit module | Fixed in 7.0.2, 6.9.5 |
| CVE-2026-60137WordPress < 7.0.2 - Facilitated SQL Injection via author__not_in in WP_Query5.9 Medium · published 17 July 2026 | On CISA's list Metasploit module | Fixed in 7.0.2, 6.9.5, 6.8.6 |
| CVE-2026-87902Remote File Inclusion8.1 High · published 22 September 2026 | On CISA's list Exploit-DB entry EPSS 0.50 or more | Fixed in 7.1.2 |
| CVE-2026-119977WordPress Core 4.7.0 - 7.1.3 - Unauthenticated Upgrade-Window Staged-Installer Remote Code Execution8.1 High · published 31 October 2026 | On CISA's list | The record names no fixed release for 7.1, 7.0, 6.9, 6.8, 6.7, 6.6, 6.5, 6.4, 6.3, 6.2, 6.1, 6.0, 5.9, 5.8, 5.7, 5.6, 5.5, 5.4, 5.3, 5.2, 5.1, 5.0, 4.9, 4.8 and 4.7. |
| CVE-2022-21661SQL injection in WordPress8.0 High · published 6 January 2022 | Exploit-DB entry EPSS 0.50 or more | Fixed in 5.8.3 |
| CVE-2021-29447WordPress Authenticated XXE attack when installation is running PHP 87.1 High · published 15 April 2021 | Exploit-DB entry EPSS 0.50 or more | This page does not place it on a branch. |
| CVE-2023-2745WordPress Core < 6.2.1 - Directory Traversal5.4 Medium · published 17 May 2023 | Exploit-DB entry EPSS 0.50 or more | Fixed in 6.2.1, 6.1.2, 6.0.4, 5.9.6, 5.8.7, 5.7.9, 5.6.11, 5.5.12, 5.4.13, 5.3.15, 5.2.18, 5.1.16, 5.0.19, 4.9.23, 4.8.22, 4.7.26And 6 more releases fix it. |
| CVE-2020-11027Password reset links invalidation issue in WordPress6.1 Medium · published 30 April 2020 | Exploit-DB entry | Fixed in 5.4.1, 5.3.3, 5.2.6, 5.1.5, 5.0.9, 4.9.14, 4.8.13, 4.7.17, 4.6.18, 4.5.21, 4.4.22, 4.3.23, 4.2.27, 4.1.30, 4.0.30, 3.9.31And 2 more releases fix it. |
| CVE-2024-4439WordPress Core is vulnerable to Stored Cross-Site Scripting via user display names in the Avatar block in various versions up to 6.5.2 due to insufficient output escaping on the display name. This…7.2 High · published 3 May 2024 | EPSS 0.50 or more | The record names no fixed release for 6.5, 6.4, 6.3, 6.2, 6.1 and 6.0. |
| CVE-2022-21662Stored XSS in WordPress8.0 High · published 6 January 2022 | EPSS 0.50 or more | Fixed in 5.8.3 |
CISA's list for the vendor
The entries CISA lists under the vendor names it uses for WordPress, each with its patch-first group.
- WordPress: exploited vulnerabilities7 entries
What this page counts
The branches, their dates and the newest release of each are from the product lifecycle data credited under Sources. A later release that a CVE record names as a fix counts as the newest too.
This page reads 52 CVE records that the CVE Numbering Authorities GitHub, Wordfence, Patchstack, WPScan, HackerOne, JPCERT/CC and MITRE published and that name WordPress. The fixes are from the 29 it places on a branch. A record says a release fixes a flaw when its affected range for a branch ends before that release. A record from any other source gives no version here.
No release of a branch that has ended is called safe here.
Some records give a range with no start: from 0, or before a release. A record is placed on the branch of the release that ends its range. As the record states it, the range also covers every older release. Such a range is not counted when the newest safe release of a branch that still gets fixes is worked out.
Some records give a range that starts in an older branch and ends in a newer one. A record is placed on the branch of the release that ends its range, and as the record states it, the range also covers the older branches it runs across. Only a range that runs across branches that have all ended is placed: a range that reaches a branch that still gets fixes would name that branch's newest release as affected, which a project that also fixes its older branches does not mean. Such a record is counted at the end of the page.
23 records are not placed on a branch, so no branch or release row counts them: CVE-2019-16780, CVE-2019-16781, CVE-2021-29447, CVE-2021-29450, CVE-2021-39200, CVE-2021-39201, CVE-2021-39202, CVE-2021-39203, CVE-2022-3590 and CVE-2022-21664 and 13 others.
Sources
- CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
- Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
- EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)