NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist
Packagist, #1047 most downloaded on Packagist
WordPress is open source software you can use to create a beautiful website, blog, or app.
Latest stable
7.1.4
Last release 8 months ago
22 Mar 2026
Ships unpredictably
gaps range from 8 days to 2.1 years
Nearly every release is documented
notes for 55 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
750 releases · first in 2018
Drag across the ruler to compare, or tap a release to open it.
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features several security fixes. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
As a courtesy, these fixes are also available in older affected branches of WordPress. As a reminder, only the most recent version of WordPress is actively supported.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features one security fix. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
WP_Http::make_absolute_url() method, reported by Anthropic{status}_{type} hook can lead to action name collision, reported by Alex Concha of the WordPress security teamAs a courtesy, these fixes are also available in older affected branches of WordPress. As a reminder, only the most recent version of WordPress is actively supported.
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features one security fix. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
As a courtesy, these fixes are also available in older affected branches of WordPress. As a reminder, only the most recent version of WordPress is actively supported.
This security and maintenance release includes 17 bug fixes on Core , 19 bug fixes for the Block Editor , and 12 security fixes.
Sourced from WordPress.org Documentation.
This release was led by Adam Silverstein, Adrian Duffell, Andrei Draganescu and Aaron Jorbin.
This security and maintenance release includes 17 bug fixes on Core, 19 bug fixes for the Block Editor, and 12 security fixes.
For a full list of bug fixes, please refer to the release candidate announcement.
This security and maintenance release features 16 bug fixes on Core, 21 bug fixes for the Block Editor, and 12 security fixes. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
As a courtesy, these fixes are also available in older affected branches of WordPress. As a reminder, only the most recent version of WordPress is actively supported.
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features several security fixes. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features one security fix. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
WP_Http::make_absolute_url() method, reported by Anthropic{status}_{type} hook can lead to action name collision, reported by Alex Concha of the WordPress security teamAs a courtesy, these fixes are also available in older affected branches of WordPress. As a reminder, only the most recent version of WordPress is actively supported.
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features one security fix. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features several security fixes. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features several security fixes. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
As a courtesy, these fixes are also available in older affected branches of WordPress. As a reminder, only the most recent version of WordPress is actively supported.
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<h3 class="wp-block-heading">Security updates</h3>
<p class="wp-block-paragraph">This release features several security fixes. Because this is a security release, <strong>it is recommended that you update your sites immediately.</strong><br>The security team would like to thank the following people for <a href="https://hackerone.com/wordpress?type=team">responsibly reporting vulnerabilities</a>, and allowing them to be fixed in this release:</p>
<ul class="wp-block-list"> <li>A Contributor+ stored cross-site scripting (XSS) issue in the Post Date block reported by Alex Concha of the WordPress Security Team</li>
<li>A Contributor+ stored cross-site scripting (XSS) issue in the Post Content block reported by n05ec</li>
<li>An information disclosure issue in the Latest Comments block exposing comments on password-protected posts reported by Ehtisham Siddiqui of the WordPress Security Team</li>
<li>A bypass of the email address confirmation flow reported by 0ways</li>
<li>An Author+ CSS injection issue via a bypass of the safe CSS attribute filter reported by Anthropic</li>
<li>A Contributor+ stored cross-site scripting (XSS) issue in posts via the emoji settings element reported by Asaf Mozes (amosec)</li>
<li>A privilege escalation issue on multisite networks with user registration enabled, allowing a user to create a new site reported by Aikido Security</li>
<li>A server-side request forgery (SSRF) issue in URL validation allowing requests to link-local ranges reported by Andrew Mohawk and multiple independent reporters</li>
<li>A pre-auth reflected cross-site scripting (XSS) issue on the login screen with potential to lead to PHP code execution reported by the team at pwn.ai</li>
<li>A disclosure of notes in comment feeds reported by Elio Gubser</li>
<li>An enumeration of post slugs reported by HDWSec</li>
<li>A Contributor+ stored cross-site scripting (XSS) issue in Quick Edit on sites with a large number of users reported by Naveen S and Ajmal Moochingal</li> </ul>
<p class="wp-block-paragraph">As a courtesy, these fixes are also available in older affected branches of WordPress. As a reminder, <strong>only the most recent version of WordPress is actively supported.</strong></p>
<ul class="wp-block-list"> <li>WordPress 6.9 is affected by 11 of the 12 vulnerabilities. <a href="https://wordpress.org/documentation/wordpress-version/version-6-9-6/">Version 6.9.6</a> has been released containing fixes.</li>
<li>WordPress 6.8 is affected by 8 of the 12 vulnerabilities. <a href="https://wordpress.org/documentation/wordpress-version/version-6-8-7/">Version 6.8.7</a> has been released containing fixes.</li>
<li>WordPress 6.7 is affected by 8 of the 12 vulnerabilities. <a href="https://wordpress.org/documentation/wordpress-version/version-6-7-6/">Version 6.7.6</a> has been released containing fixes.</li>
<li>WordPress 6.6 is affected by 8 of the 12 vulnerabilities. <a href="https://wordpress.org/documentation/wordpress-version/version-6-6-6/">Version 6.6.6</a> has been released containing fixes.</li>
<li>WordPress 6.5 is affected by 8 of the 12 vulnerabilities. <a href="https://wordpress.org/documentation/wordpress-version/version-6-5-9/">Version 6.5.9</a> has been released containing fixes.</li>
<li>WordPress 6.4 is affected by 8 of the 12 vulnerabilities. <a href="https://wordpress.org/documentation/wordpress-version/version-6-4-9/">Version 6.4.9</a> has been released containing fixes.</li>
<li>WordPress 6.3 is affected by 8 of the 12 vulnerabilities. <a href="https://wordpress.org/documentation/wordpress-version/version-6-3-9/">Version 6.3.9</a> has been released containing fixes.</li>
<li>WordPress 6.2 is affected by 8 of the 12 vulnerabilities. <a href="https://wordpress.org/documentation/wordpress-version/version-6-2-10/">Version 6.2.10</a> has been released containing fixes.</li>
<li>WordPress 6.1 is affected by 8 of the 12 vulnerabilities. <a href="https://wordpress.org/documentation/wordpress-version/version-6-1-11/">Version 6.1.11</a> has been released containing fixes.</li>
<li>WordPress 6.0 is affected by 8 of the 12 vulnerabilities. <a href="https://wordpress.org/documentation/wordpress-version/version-6-0-13/">Version 6.0.13</a> has been released containing fixes.</li>
<li>WordPress 5.9 is affected by 8 of the 12 vulnerabilities. <a href="https://wordpress.org/documentation/wordpress-version/version-5-9-14/">Version 5.9.14</a> has been released containing fixes.</li>
<li>WordPress 5.8 is affected by 8 of the 12 vulnerabilities. <a href="https://wordpress.org/documentation/wordpress-version/version-5-8-14/">Version 5.8.14</a> has been released containing fixes.</li>
<li>WordPress 5.7 is affected by 7 of the 12 vulnerabilities. <a href="https://wordpress.org/documentation/wordpress-version/version-5-7-16/">Version 5.7.16</a> has been released containing fixes.</li>
<li>WordPress 5.6 is affected by 7 of the 12 vulnerabilities. <a href="https://wordpress.org/documentation/wordpress-version/version-5-6-18/">Version 5.6.18</a> has been released containing fixes.</li>
<li>WordPress 5.5 is affected by 7 of the 12 vulnerabilities. <a href="https://wordpress.org/documentation/wordpress-version/version-5-5-19/">Version 5.5.19</a> has been released containing fixes.</li>
<li>WordPress 5.4 is affected by 7 of the 12 vulnerabilities. <a href="https://wordpress.org/documentation/wordpress-version/version-5-4-20/">Version 5.4.20</a> has been released containing fixes.</li>
<li>WordPress 5.3 is affected by 7 of the 12 vulnerabilities. <a href="https://wordpress.org/documentation/wordpress-version/version-5-3-22/">Version 5.3.22</a> has been released containing fixes.</li>
<li>WordPress 5.2 is affected by 7 of the 12 vulnerabilities. <a href="https://wordpress.org/documentation/wordpress-version/version-5-2-25/">Version 5.2.25</a> has been released containing fixes.</li>
<li>WordPress 5.1 is affected by 7 of the 12 vulnerabilities. <a href="https://wordpress.org/documentation/wordpress-version/version-5-1-23/">Version 5.1.23</a> has been released containing fixes.</li>
<li>WordPress 5.0 is affected by 7 of the 12 vulnerabilities. <a href="https://wordpress.org/documentation/wordpress-version/version-5-0-26/">Version 5.0.26</a> has been released containing fixes.</li>
<li>WordPress 4.9 is affected by 7 of the 12 vulnerabilities. <a href="https://wordpress.org/documentation/wordpress-version/version-4-9-30/">Version 4.9.30</a> has been released containing fixes.</li>
<li>WordPress 4.8 is affected by 7 of the 12 vulnerabilities. <a href="https://wordpress.org/documentation/wordpress-version/version-4-8-29/">Version 4.8.29</a> has been released containing fixes.</li>
<li>WordPress 4.7 is affected by 7 of the 12 vulnerabilities. <a href="https://wordpress.org/documentation/wordpress-version/version-4-7-34/">Version 4.7.34</a> has been released containing fixes.</li>
<li>WordPress 4.6 and earlier no longer receive security updates.</li> </ul>
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<h3 class="wp-block-heading">Security updates</h3>
<p class="wp-block-paragraph">This release features several security fixes. Because this is a security release, <strong>it is recommended that you update your sites immediately.</strong><br>The security team would like to thank the following people for <a href="https://hackerone.com/wordpress?type=team">responsibly reporting vulnerabilities</a>, and allowing them to be fixed in this release:</p>
<ul class="wp-block-list"> <li>A facilitated SQL injection issue reported by as a team by TF1T, dtro, and haongo</li>
<li>A REST API batch-route confusion and SQL injection issue leading to Remote Code Execution reported by Adam Kues at <a href="https://slcyber.io"><u>Assetnote / Searchlight Cyber</u></a></li> </ul>
<p class="wp-block-paragraph">As a courtesy, these fixes are available in affected branches of WordPress to eligible to receive security fixes (currently through 4.7). As a reminder, <strong>only the most recent version of WordPress is actively supported</strong>.</p>
_Sourced from WordPress.org Documentation._
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<p class="wp-block-paragraph">This release was led by <a href="https://profiles.wordpress.org/jorbin/">Aaron Jorbin</a>, <a href="https://profiles.wordpress.org/masteradhoc/">Brian Haas</a>, <a href="https://profiles.wordpress.org/cbravobernal/">Carlos Bravo</a> and <a href="https://profiles.wordpress.org/estelaris/">Estela Rueda</a>.</p>
<p class="wp-block-paragraph">This minor release includes fixes for 31 bugs <a href="https://core.trac.wordpress.org/query?resolution=fixed&milestone=7.0.1&group=component&col=id&col=summary&col=milestone&col=owner&col=type&col=status&col=priority&order=priority">throughout Core</a> and the <a href="https://core.trac.wordpress.org/changeset/62610">Block Editor</a>, addressing issues affecting multiple areas of WordPress including the block editor, mail, and classic themes.</p>
<p class="wp-block-paragraph">For a full list of bug fixes, please refer to the <a href="https://make.wordpress.org/core/2026/07/01/wordpress-7-0-1-rc1-is-now-available/">release candidate announcement.</a></p>
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features several security fixes. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features one security fix. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
WP_Http::make_absolute_url() method, reported by Anthropic{status}_{type} hook can lead to action name collision, reported by Alex Concha of the WordPress security teamAs a courtesy, these fixes are also available in older affected branches of WordPress. As a reminder, only the most recent version of WordPress is actively supported.
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features one security fix. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features several security fixes. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features several security fixes. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<h3 class="wp-block-heading">Security updates</h3>
<p class="wp-block-paragraph">This release features several security fixes. Because this is a security release, <strong>it is recommended that you update your sites immediately.</strong><br>The security team would like to thank the following people for <a href="https://hackerone.com/wordpress?type=team">responsibly reporting vulnerabilities</a>, and allowing them to be fixed in this release:</p>
<ul class="wp-block-list"> <li>A Contributor+ stored cross-site scripting (XSS) issue in the Post Date block reported by Alex Concha of the WordPress Security Team</li>
<li>A Contributor+ stored cross-site scripting (XSS) issue in the Post Content block reported by n05ec</li>
<li>A bypass of the email address confirmation flow reported by 0ways</li>
<li>An Author+ CSS injection issue via a bypass of the safe CSS attribute filter reported by Anthropic</li>
<li>A Contributor+ stored cross-site scripting (XSS) issue in posts via the emoji settings element reported by Asaf Mozes (amosec)</li>
<li>A privilege escalation issue on multisite networks with user registration enabled, allowing a user to create a new site reported by Aikido Security</li>
<li>A server-side request forgery (SSRF) issue in URL validation allowing requests to link-local ranges reported by Andrew Mohawk and multiple independent reporters</li>
<li>A pre-auth reflected cross-site scripting (XSS) issue on the login screen with potential to lead to PHP code execution reported by the team at pwn.ai</li>
<li>A disclosure of notes in comment feeds reported by Elio Gubser</li>
<li>An enumeration of post slugs reported by HDWSec</li>
<li>A Contributor+ stored cross-site scripting (XSS) issue in Quick Edit on sites with a large number of users reported by Naveen S and Ajmal Moochingal</li> </ul>
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<h3 class="wp-block-heading">Security updates</h3>
<p class="wp-block-paragraph">This release features several security fixes. Because this is a security release, <strong>it is recommended that you update your sites immediately.</strong><br>The security team would like to thank the following people for <a href="https://hackerone.com/wordpress?type=team">responsibly reporting vulnerabilities</a>, and allowing them to be fixed in this release:</p>
<ul class="wp-block-list"> <li>A facilitated SQL injection issue reported as a team by TF1T, dtro, and haongo</li>
<li>A REST API batch-route confusion and SQL injection issue leading to Remote Code Execution reported by Adam Kues at <a href="https://slcyber.io"><u>Assetnote / Searchlight Cyber</u></a></li> </ul>
<p class="wp-block-paragraph">As a courtesy, these fixes are available in affected branches of WordPress to eligible to receive security fixes (currently through 4.7). As a reminder, <strong>only the most recent version of WordPress is actively supported</strong>.</p>
This release features several security fixes that were not fully applied to the 6.9.2 release. Because this is a security release, it is recommended t…
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<h3 id="maintenance-updates" class="wp-block-heading">Security updates</h3>
<p class="wp-block-paragraph">This release features several security fixes that were not fully applied to the 6.9.2 release. Because this is a security release, <strong>it is recommended that you update your sites immediately.</strong></p>
<p class="wp-block-paragraph">The security team would like to thank the following people for <a href="https://hackerone.com/wordpress?type=team">responsibly reporting vulnerabilities</a>, and allowing them to be fixed in this release:</p>
<ul class="wp-block-list"> <li>A PclZip path traversal issue reported independently by <a href="https://profiles.wordpress.org/francescocarlucci/">Francesco Carlucci</a> and <a href="https://profiles.wordpress.org/kaminuma/">kaminuma</a></li>
<li>An authorization bypass on the Notes feature reported by <a href="https://profiles.wordpress.org/kaminuma/">kaminuma</a></li>
<li>An XXE in the external getID3 library reported by <a href="https://profiles.wordpress.org/regex33/">Youssef Achtatal</a></li>
<li><a href="https://profiles.wordpress.org/kraftner">Thomas Kräftner</a> for his responsible disclosure</li> </ul>
<p class="wp-block-paragraph">The WordPress security team have worked with the maintainer of the external getID3 library, James Heinrich, to coordinate a fix to getID3. A new version of getID3 <a href="https://github.com/JamesHeinrich/getID3/releases">is available here</a>.</p>
…template file paths that broke in the 6.9.2 security release . Although this is is not an officially supported approach to loading template files in W…
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<p class="wp-block-paragraph">This release features a bugfix for some themes that use an unusual “stringable object” mechanism when loading template file paths that broke in <a href="https://wordpress.org/documentation/wordpress-version/version-6-9-2/">the 6.9.2 security release</a>. Although this is is not an officially supported approach to loading template files in WordPress (the <code>template_include</code> filter only accepts a string), it nevertheless caused some sites to break so the team have decided to address this in a fast follow 6.9.3 release. Users using affected themes should update to 6.9.3 to restore the front end of their site to an operational state.</p>
<p class="wp-block-paragraph">As a reminder, the earlier 6.9.2 version was a security release, and <strong>only the most recent version of WordPress is actively supported</strong>.</p>
This release features several security fixes. Because this is a security release, it is recommended that you update your sites immediately.
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<h3 id="maintenance-updates" class="wp-block-heading">Security updates</h3>
<p class="wp-block-paragraph">This release features several security fixes. Because this is a security release, <strong>it is recommended that you update your sites immediately.</strong></p>
<p class="wp-block-paragraph">The security team would like to thank the following people for <a href="https://hackerone.com/wordpress?type=team">responsibly reporting vulnerabilities</a>, and allowing them to be fixed in this release:</p>
<ul class="wp-block-list"> <li>A Blind SSRF issue reported by <a href="https://hackerone.com/sibwtf">sibwtf</a>, and subsequently by several other researchers while the fix was being worked on</li>
<li>A PoP-chain weakness in the HTML API and Block Registry reported by <a href="https://github.com/hackerlo2003">Phat RiO</a></li>
<li>A regex DoS weakness in numeric character references reported by Dennis Snell of the WordPress Security Team</li>
<li>A stored XSS in nav menus reported by <a href="https://x.com/Savphill">Phill Savage</a></li>
<li>An AJAX <code>query-attachments</code> authorization bypass reported by <a href="https://www.vitalysim.com/">Vitaly Simonovich</a></li>
<li>A stored XSS via the <code>data-wp-bind</code> directive reported by <a href="https://profiles.wordpress.org/kaminuma/">kaminuma</a></li>
<li>An XSS that allows overridding client-side templates in the admin area reported by <a href="https://hackerone.com/amosec">Asaf Mozes</a></li>
<li>A PclZip path traversal issue reported independently by <a href="https://profiles.wordpress.org/francescocarlucci/">Francesco Carlucci</a> and <a href="https://profiles.wordpress.org/kaminuma/">kaminuma</a></li>
<li>An authorization bypass on the Notes feature reported by <a href="https://profiles.wordpress.org/kaminuma/">kaminuma</a></li>
<li>An XXE in the external getID3 library reported by <a href="https://profiles.wordpress.org/regex33/">Youssef Achtatal</a></li> </ul>
<p class="wp-block-paragraph">The WordPress security team have worked with the maintainer of the external getID3 library, James Heinrich, to coordinate a fix to getID3. A new version of getID3 <a href="https://github.com/JamesHeinrich/getID3/releases">is available here</a>.<br>As a courtesy, these fixes are being backported, where necessary, to all branches eligible to receive security fixes (currently through 4.7). As a reminder, <strong>only the most recent version of WordPress is actively supported</strong>.</p>
_Sourced from WordPress.org Documentation._
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading"><a href="https://wordpress.org/documentation/wordpress-version/version-6-8-1/#summary">Summary</a></h2>
<p class="wp-block-paragraph">This release was led by <a href="https://profiles.wordpress.org/jorbin/">Aaron Jorbin</a> and <a href="https://profiles.wordpress.org/wildworks">Aki Hamano.</a></p>
<p class="wp-block-paragraph">This minor release includes fixes for 49 bugs <a href="https://core.trac.wordpress.org/query?resolution=fixed&milestone=6.9.1&group=component&col=id&col=summary&col=milestone&col=owner&col=type&col=status&col=priority&order=priority">throughout Core</a> and <a href="https://github.com/WordPress/gutenberg/pull/74806">the Block Editor</a>, addressing issues affecting multiple areas of WordPress including the block editor, mail, and classic themes.</p>
<p class="wp-block-paragraph">For a full list of bug fixes, please refer to the <a href="https://make.wordpress.org/core/2026/01/30/wordpress-6-9-1-rc1-is-now-available/">release candidate announcement.</a></p>
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features several security fixes. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features one security fix. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
WP_Http::make_absolute_url() method, reported by Anthropic{status}_{type} hook can lead to action name collision, reported by Alex Concha of the WordPress security teamAs a courtesy, these fixes are also available in older affected branches of WordPress. As a reminder, only the most recent version of WordPress is actively supported.
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features one security fix. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features several security fixes. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features several security fixes. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<h3 class="wp-block-heading">Security updates</h3>
<p class="wp-block-paragraph">This release features several security fixes. Because this is a security release, <strong>it is recommended that you update your sites immediately.</strong><br>The security team would like to thank the following people for <a href="https://hackerone.com/wordpress?type=team">responsibly reporting vulnerabilities</a>, and allowing them to be fixed in this release:</p>
<ul class="wp-block-list"> <li>A Contributor+ stored cross-site scripting (XSS) issue in the Post Date block reported by Alex Concha of the WordPress Security Team</li>
<li>A bypass of the email address confirmation flow reported by 0ways</li>
<li>An Author+ CSS injection issue via a bypass of the safe CSS attribute filter reported by Anthropic</li>
<li>A privilege escalation issue on multisite networks with user registration enabled, allowing a user to create a new site reported by Aikido Security</li>
<li>A server-side request forgery (SSRF) issue in URL validation allowing requests to link-local ranges reported by Andrew Mohawk and multiple independent reporters</li>
<li>A pre-auth reflected cross-site scripting (XSS) issue on the login screen with potential to lead to PHP code execution reported by the team at pwn.ai</li>
<li>An enumeration of post slugs reported by HDWSec</li>
<li>A Contributor+ stored cross-site scripting (XSS) issue in Quick Edit on sites with a large number of users reported by Naveen S and Ajmal Moochingal</li> </ul>
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<h3 class="wp-block-heading">Security updates</h3>
<p class="wp-block-paragraph">This release features several security fixes. Because this is a security release, <strong>it is recommended that you update your sites immediately.</strong><br>The security team would like to thank the following people for <a href="https://hackerone.com/wordpress?type=team">responsibly reporting vulnerabilities</a>, and allowing them to be fixed in this release:</p>
<ul class="wp-block-list"> <li>A facilitated SQL injection issue reported as a team by TF1T, dtro, and haongo</li>
<li>A REST API batch-route confusion and SQL injection issue leading to Remote Code Execution reported by Adam Kues at <a href="https://slcyber.io"><u>Assetnote / Searchlight Cyber</u></a></li> </ul>
<p class="wp-block-paragraph">As a courtesy, these fixes are available in affected branches of WordPress to eligible to receive security fixes (currently through 4.7). As a reminder, <strong>only the most recent version of WordPress is actively supported</strong>.</p>
This release features several security fixes. Because this is a security release, it is recommended that you update your sites immediately.
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<h3 id="maintenance-updates" class="wp-block-heading">Security updates</h3>
<p class="wp-block-paragraph">This release features several security fixes. Because this is a security release, <strong>it is recommended that you update your sites immediately.</strong></p>
<p class="wp-block-paragraph">The security team would like to thank the following people for <a href="https://hackerone.com/wordpress?type=team">responsibly reporting vulnerabilities</a>, and allowing them to be fixed in this release:</p>
<ul class="wp-block-list"> <li>A Blind SSRF issue reported by <a href="https://hackerone.com/sibwtf">sibwtf</a>, and subsequently by several other researchers while the fix was being worked on</li>
<li>A PoP-chain weakness in the HTML API and Block Registry reported by <a href="https://github.com/hackerlo2003">Phat RiO</a></li>
<li>A regex DoS weakness in numeric character references reported by Dennis Snell of the WordPress Security Team</li>
<li>A stored XSS in nav menus reported by <a href="https://x.com/Savphill">Phill Savage</a></li>
<li>An AJAX <code>query-attachments</code> authorization bypass reported by <a href="https://www.vitalysim.com/">Vitaly Simonovich</a></li>
<li>A stored XSS via the <code>data-wp-bind</code> directive reported by <a href="https://profiles.wordpress.org/kaminuma/">kaminuma</a></li>
<li>An XSS that allows overridding client-side templates in the admin area reported by <a href="https://hackerone.com/amosec">Asaf Mozes</a></li>
<li>A PclZip path traversal issue reported independently by <a href="https://profiles.wordpress.org/francescocarlucci/">Francesco Carlucci</a> and <a href="https://profiles.wordpress.org/kaminuma/">kaminuma</a></li>
<li>An XXE in the external getID3 library reported by <a href="https://profiles.wordpress.org/regex33/">Youssef Achtatal</a></li> </ul>
<p class="wp-block-paragraph">The WordPress security team have worked with the maintainer of the external getID3 library, James Heinrich, to coordinate a fix to getID3. A new version of getID3 <a href="https://github.com/JamesHeinrich/getID3/releases">is available here</a>.<br>As a courtesy, these fixes are being backported, where necessary, to all branches eligible to receive security fixes (currently through 4.7). As a reminder, <strong>only the most recent version of WordPress is actively supported</strong>.</p>
_Version notes available on WordPress.org Documentation._
Version notes available on WordPress.org Documentation.
_Sourced from WordPress.org Documentation._
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<p>This release was led by <a href="https://profiles.wordpress.org/audrasjb/">JB Audras</a>, <a href="https://profiles.wordpress.org/estelaris/">Estela Rueda</a> and <a href="https://profiles.wordpress.org/zunaid321/">Zunaid Amin</a></p>
<p>This minor release includes fixes for <a href="https://core.trac.wordpress.org/query?resolution=fixed&milestone=6.8.2&group=component&col=id&col=summary&col=milestone&col=owner&col=type&col=status&col=priority&order=priority">20 Core tickets</a> and <a href="https://github.com/WordPress/gutenberg/pull/70557">15 Block Editor issues</a>. For a full list of bug fixes, please refer to the <a href="https://wordpress.org/news/2025/07/wordpress-6-8-2-maintenance-release/">release announcement</a>.</p>
_Sourced from WordPress.org Documentation._
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading" id="summary">Summary</h2>
<p>This release was led by <a href="https://profiles.wordpress.org/jorbin/">Aaron Jorbin</a>.</p>
<p>This minor release includes fixes for 15 bugs <a href="https://core.trac.wordpress.org/query?resolution=fixed&milestone=6.8.1&group=component&col=id&col=summary&col=milestone&col=owner&col=type&col=status&col=priority&order=priority">throughout Core</a> and <a href="https://github.com/WordPress/wordpress-develop/pull/8752">the Block Editor</a> addressing issues affecting multiple areas of WordPress including the block editor, multisite, and REST API. </p>
<p>For a full list of bug fixes, please refer to the <a href="https://make.wordpress.org/core/2025/04/28/wordpress-6-8-1-rc1-is-now-available/">release candidate announcement.</a></p>
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features several security fixes. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features one security fix. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
WP_Http::make_absolute_url() method, reported by Anthropic{status}_{type} hook can lead to action name collision, reported by Alex Concha of the WordPress security teamAs a courtesy, these fixes are also available in older affected branches of WordPress. As a reminder, only the most recent version of WordPress is actively supported.
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features one security fix. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features several security fixes. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features several security fixes. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<h3 class="wp-block-heading">Security updates</h3>
<p class="wp-block-paragraph">This release features several security fixes. Because this is a security release, <strong>it is recommended that you update your sites immediately.</strong><br>The security team would like to thank the following people for <a href="https://hackerone.com/wordpress?type=team">responsibly reporting vulnerabilities</a>, and allowing them to be fixed in this release:</p>
<ul class="wp-block-list"> <li>A Contributor+ stored cross-site scripting (XSS) issue in the Post Date block reported by Alex Concha of the WordPress Security Team</li>
<li>A bypass of the email address confirmation flow reported by 0ways</li>
<li>An Author+ CSS injection issue via a bypass of the safe CSS attribute filter reported by Anthropic</li>
<li>A privilege escalation issue on multisite networks with user registration enabled, allowing a user to create a new site reported by Aikido Security</li>
<li>A server-side request forgery (SSRF) issue in URL validation allowing requests to link-local ranges reported by Andrew Mohawk and multiple independent reporters</li>
<li>A pre-auth reflected cross-site scripting (XSS) issue on the login screen with potential to lead to PHP code execution reported by the team at pwn.ai</li>
<li>An enumeration of post slugs reported by HDWSec</li>
<li>A Contributor+ stored cross-site scripting (XSS) issue in Quick Edit on sites with a large number of users reported by Naveen S and Ajmal Moochingal</li> </ul>
This release features several security fixes. Because this is a security release, it is recommended that you update your sites immediately.
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<h3 id="maintenance-updates" class="wp-block-heading">Security updates</h3>
<p class="wp-block-paragraph">This release features several security fixes. Because this is a security release, <strong>it is recommended that you update your sites immediately.</strong></p>
<p class="wp-block-paragraph">The security team would like to thank the following people for <a href="https://hackerone.com/wordpress?type=team">responsibly reporting vulnerabilities</a>, and allowing them to be fixed in this release:</p>
<ul class="wp-block-list"> <li>A Blind SSRF issue reported by <a href="https://hackerone.com/sibwtf">sibwtf</a>, and subsequently by several other researchers while the fix was being worked on</li>
<li>A PoP-chain weakness in the HTML API and Block Registry reported by <a href="https://github.com/hackerlo2003">Phat RiO</a></li>
<li>A regex DoS weakness in numeric character references reported by Dennis Snell of the WordPress Security Team</li>
<li>A stored XSS in nav menus reported by <a href="https://x.com/Savphill">Phill Savage</a></li>
<li>An AJAX <code>query-attachments</code> authorization bypass reported by <a href="https://www.vitalysim.com/">Vitaly Simonovich</a></li>
<li>A stored XSS via the <code>data-wp-bind</code> directive reported by <a href="https://profiles.wordpress.org/kaminuma/">kaminuma</a></li>
<li>An XSS that allows overridding client-side templates in the admin area reported by <a href="https://hackerone.com/amosec">Asaf Mozes</a></li>
<li>A PclZip path traversal issue reported independently by <a href="https://profiles.wordpress.org/francescocarlucci/">Francesco Carlucci</a> and <a href="https://profiles.wordpress.org/kaminuma/">kaminuma</a></li>
<li>An XXE in the external getID3 library reported by <a href="https://profiles.wordpress.org/regex33/">Youssef Achtatal</a></li> </ul>
<p class="wp-block-paragraph">The WordPress security team have worked with the maintainer of the external getID3 library, James Heinrich, to coordinate a fix to getID3. A new version of getID3 <a href="https://github.com/JamesHeinrich/getID3/releases">is available here</a>.<br>As a courtesy, these fixes are being backported, where necessary, to all branches eligible to receive security fixes (currently through 4.7). As a reminder, <strong>only the most recent version of WordPress is actively supported</strong>.</p>
This release features 2 security fixes. Because this is a security release, it is recommended that you update your sites immediately.
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<h3 class="wp-block-heading" id="maintenance-updates">Security updates</h3>
<p>This release features 2 security fixes. Because this is a security release, <strong>it is recommended that you update your sites immediately.</strong></p>
<p>The security team would like to thank the following people for <a href="https://hackerone.com/wordpress?type=team">responsibly reporting vulnerabilities</a>, and allowing them to be fixed in this release:</p>
<ul class="wp-block-list"> <li>A data exposure issue where authenticated users could access some restricted content. Independently reported by <a href="https://hackerone.com/mnelson4">Mike Nelson</a>, <a href="https://hackerone.com/hurayraiit">Abu Hurayra</a>, <a href="https://profiles.wordpress.org/timothyblynjacobs/">Timothy Jacobs</a> and <a href="https://profiles.wordpress.org/peterwilsoncc/">Peter Wilson</a>.</li>
<li>A cross-site scripting (XSS) vulnerability requiring an authenticated role that affects the nav menus. Reported by <a href="https://x.com/Savphill">Phill Savage</a>.</li> </ul>
<p>As a courtesy to users on older branches of WordPress, these fixes are available in branches of WordPress going back to WordPress 4.7.</p>
_Sourced from WordPress.org Documentation._
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<p>This minor release includes an update to the root security certificate bundle. Please refer to the <a href="https://wordpress.org/news/2025/08/maintenance-releases-for-wordpress-branches-4-7-to-6-7/">release announcement</a> for further info.</p>
_Sourced from WordPress.org Documentation._
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading"><strong>Summary</strong></h2>
<p>This release was led by <a href="https://profiles.wordpress.org/jorbin/">Aaron Jorbin</a></p>
<p>WordPress 6.7.2 is a maintenance release featuring <a href="https://make.wordpress.org/core/tag/6-7-2/">35 bug fixes</a> with a strict focus on bugs introduced in WordPress 6.7.</p>
<p>For more information, <a href="https://core.trac.wordpress.org/query?resolution=fixed&milestone=6.7.2&group=component&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority">browse the full list of changes on Trac</a>.</p>
<p>WordPress 6.7.2 would not have been possible without the contributions of the following people. Their asynchronous coordination to deliver maintenance fixes into a stable release is a testament to the power and capability of the WordPress community.</p>
<p class="has-small-font-size"><a href="https://profiles.wordpress.org/jorbin">Aaron Jorbin</a>, <a href="https://profiles.wordpress.org/ajlende">Alex Lende</a>, <a href="https://profiles.wordpress.org/alexandrebuffet">Alexandre Buffet</a>, <a href="https://profiles.wordpress.org/bowedk">Andreas Pedersen</a>, <a href="https://profiles.wordpress.org/azaozz">Andrew Ozz</a>, <a href="https://profiles.wordpress.org/ankitkumarshah">Ankit Kumar Shah</a>, <a href="https://profiles.wordpress.org/apermo">apermo</a>, <a href="https://profiles.wordpress.org/benniledl">Benedikt Ledl</a>, <a href="https://profiles.wordpress.org/bernhard-reiter">bernhard-reiter</a>, <a href="https://profiles.wordpress.org/ironprogrammer">Brian Alexander</a>, <a href="https://profiles.wordpress.org/cbravobernal">Carlos Bravo</a>, <a href="https://profiles.wordpress.org/poena">Carolina Nymark</a>, <a href="https://profiles.wordpress.org/coquardcyr">Cyrille</a>, <a href="https://profiles.wordpress.org/danielpost">Daniel Post</a>, <a href="https://profiles.wordpress.org/darerodz">darerodz</a>, <a href="https://profiles.wordpress.org/dpcalhoun">David Calhoun</a>, <a href="https://profiles.wordpress.org/get_dave">David Smith</a>, <a href="https://profiles.wordpress.org/dmsnell">Dennis Snell</a>, <a href="https://profiles.wordpress.org/dhewercorus">dhewercorus</a>, <a href="https://profiles.wordpress.org/dd32">Dion Hulse</a>, <a href="https://profiles.wordpress.org/dougwollison">Doug Wollison</a>, <a href="https://profiles.wordpress.org/ellatrix">Ella</a>, <a href="https://profiles.wordpress.org/im3dabasia1">Eshaan Dabasiya</a>, <a href="https://profiles.wordpress.org/fabiankaegy">Fabian Kägy</a>, <a href="https://profiles.wordpress.org/gaambo">Fabian Todt</a>, <a href="https://profiles.wordpress.org/flixos90">Felix Arntz</a>, <a href="https://profiles.wordpress.org/ffffelix">Felix Renicks</a>, <a href="https://profiles.wordpress.org/franciscabusas22">Francis Cabusas</a>, <a href="https://profiles.wordpress.org/frankbiganski">Frank B.</a>, <a href="https://profiles.wordpress.org/mamaduka">George Mamadashvili</a>, <a href="https://profiles.wordpress.org/ghinamt">ghinamt</a>, <a href="https://profiles.wordpress.org/glynnquelch">Glynn Quelch</a>, <a href="https://profiles.wordpress.org/gziolo">Greg Ziółkowski</a>, <a href="https://profiles.wordpress.org/jameskoster">James Koster</a>, <a href="https://profiles.wordpress.org/jsnajdr">Jarda Snajdr</a>, <a href="https://profiles.wordpress.org/audrasjb">Jb Audras</a>, <a href="https://profiles.wordpress.org/jdnd">jdnd</a>, <a href="https://profiles.wordpress.org/jeryj">jeryj</a>, <a href="https://profiles.wordpress.org/joedolson">Joe Dolson</a>, <a href="https://profiles.wordpress.org/joemcgill">Joe McGill</a>, <a href="https://profiles.wordpress.org/jonsurrell">Jon Surrell</a>, <a href="https://profiles.wordpress.org/desrosj">Jonathan Desrosiers</a>, <a href="https://profiles.wordpress.org/juanwp22">juanwp22</a>, <a href="https://profiles.wordpress.org/jrf">Juliette Reinders Folmer</a>, <a href="https://profiles.wordpress.org/karthickmurugan">Karthick</a>, <a href="https://profiles.wordpress.org/mt8biz">Kazuto Takeshita</a>, <a href="https://profiles.wordpress.org/ryelle">Kelly Choyce-Dwan</a>, <a href="https://profiles.wordpress.org/ketanniruke">Ketan Niruke</a>, <a href="https://profiles.wordpress.org/0mirka00">Lena Morita</a>, <a href="https://profiles.wordpress.org/levskipg">levskipg</a>, <a href="https://profiles.wordpress.org/maciejmackowiak">Maciej Ma?kowiak</a>, <a href="https://profiles.wordpress.org/santosguillamot">Mario Santos</a>, <a href="https://profiles.wordpress.org/mboynes">Matthew Boynes</a>, <a href="https://profiles.wordpress.org/mayanktripathi32">Mayank Tripathi</a>, <a href="https://profiles.wordpress.org/czapla">Michal Czaplinski</a>, <a href="https://profiles.wordpress.org/mcsf">Miguel Fonseca</a>, <a href="https://profiles.wordpress.org/presstoke">Mitchell Austin</a>, <a href="https://profiles.wordpress.org/mreishus">mreishus</a>, <a href="https://profiles.wordpress.org/mukesh27">Mukesh Panchal</a>, <a href="https://profiles.wordpress.org/assassinateur">Nadir Seghir a11n</a>, <a href="https://profiles.wordpress.org/narenin">Narendra Sishodiya</a>, <a href="https://profiles.wordpress.org/nareshbheda">Naresh Bheda</a>, <a href="https://profiles.wordpress.org/neotrope">neotrope</a>, <a href="https://profiles.wordpress.org/ndiego">Nick Diego</a>, <a href="https://profiles.wordpress.org/oglekler">Olga Gleckler</a>, <a href="https://profiles.wordpress.org/parthvataliya">Parth vataliya</a>, <a href="https://profiles.wordpress.org/swissspidy">Pascal Birchler</a>, <a href="https://profiles.wordpress.org/paullb">paullb</a>, <a href="https://profiles.wordpress.org/peterwilsoncc">Peter Wilson</a>, <a href="https://profiles.wordpress.org/pitamdey">Pitam Dey</a>, <a href="https://profiles.wordpress.org/redkite">redkite</a>, <a href="https://profiles.wordpress.org/rishavdutta">Rishav Dutta</a>, <a href="https://profiles.wordpress.org/robertstaddon">robertstaddon</a>, <a href="https://profiles.wordpress.org/rvoigt">rvoigt</a>, <a href="https://profiles.wordpress.org/mi5t4n">Sagar Tamang</a>, <a href="https://profiles.wordpress.org/sainathpoojary">Sainath Poojary</a>, <a href="https://profiles.wordpress.org/seanlanglands">seanlanglands</a>, <a href="https://profiles.wordpress.org/SergeyBiryukov">Sergey Biryukov</a>, <a href="https://profiles.wordpress.org/coffee2code/">Scott Reilly</a>, <a href="https://profiles.wordpress.org/shyamkariya">Shyam Kariya</a>, <a href="https://profiles.wordpress.org/smerriman">smerriman</a>, <a href="https://profiles.wordpress.org/sabernhardt">Stephen Bernhardt</a>, <a href="https://profiles.wordpress.org/sukhendu2002">Sukhendu Sekhar Guria</a>, <a href="https://profiles.wordpress.org/TobiasBg">TobiasBg</a>, <a href="https://profiles.wordpress.org/hellofromTonya">Tonya Mork</a>, <a href="https://profiles.wordpress.org/vishy-moghan">Vishy Moghan</a>, <a href="https://profiles.wordpress.org/westonruter">Weston Ruter</a>, <a href="https://profiles.wordpress.org/wongjn">wongjn</a>, <a href="https://profiles.wordpress.org/yogeshbhutkar">Yogesh Bhutkar</a>, <a href="https://profiles.wordpress.org/zaoyao">zaoyao</a></p>
_Sourced from WordPress.org Documentation._
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<p>This release was led by <a href="https://profiles.wordpress.org/desrosj/">Jonathan Desrosiers</a> and <a href="https://profiles.wordpress.org/cbravobernal/">Carlos Bravo</a>.</p>
<p>WordPress 6.7.1 is a fast-follow release featuring 16 bug fixes <a href="https://core.trac.wordpress.org/query?resolution=fixed&milestone=6.7.1&group=component&col=id&col=summary&col=milestone&col=owner&col=type&col=status&col=priority&order=priority">throughout Core</a> and <a href="https://github.com/WordPress/wordpress-develop/pull/7851">the Block Editor</a> with a strict focus on bugs introduced in WordPress 6.7. </p>
<p>You can review a summary of the maintenance updates in this release by reading the <a href="https://make.wordpress.org/core/2024/11/20/wordpress-6-7-1-rc1-is-now-available/">Release Candidate announcement</a>.</p>
<p>For more information, <a href="https://core.trac.wordpress.org/query?resolution=fixed&milestone=6.7.1&group=component&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority">browse the full list of changes on Trac</a>.</p>
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features several security fixes. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features one security fix. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
WP_Http::make_absolute_url() method, reported by Anthropic{status}_{type} hook can lead to action name collision, reported by Alex Concha of the WordPress security teamAs a courtesy, these fixes are also available in older affected branches of WordPress. As a reminder, only the most recent version of WordPress is actively supported.
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features one security fix. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features several security fixes. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features several security fixes. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<h3 class="wp-block-heading">Security updates</h3>
<p class="wp-block-paragraph">This release features several security fixes. Because this is a security release, <strong>it is recommended that you update your sites immediately.</strong><br>The security team would like to thank the following people for <a href="https://hackerone.com/wordpress?type=team">responsibly reporting vulnerabilities</a>, and allowing them to be fixed in this release:</p>
<ul class="wp-block-list"> <li>A Contributor+ stored cross-site scripting (XSS) issue in the Post Date block reported by Alex Concha of the WordPress Security Team</li>
<li>A bypass of the email address confirmation flow reported by 0ways</li>
<li>An Author+ CSS injection issue via a bypass of the safe CSS attribute filter reported by Anthropic</li>
<li>A privilege escalation issue on multisite networks with user registration enabled, allowing a user to create a new site reported by Aikido Security</li>
<li>A server-side request forgery (SSRF) issue in URL validation allowing requests to link-local ranges reported by Andrew Mohawk and multiple independent reporters</li>
<li>A pre-auth reflected cross-site scripting (XSS) issue on the login screen with potential to lead to PHP code execution reported by the team at pwn.ai</li>
<li>An enumeration of post slugs reported by HDWSec</li>
<li>A Contributor+ stored cross-site scripting (XSS) issue in Quick Edit on sites with a large number of users reported by Naveen S and Ajmal Moochingal</li> </ul>
This release features several security fixes. Because this is a security release, it is recommended that you update your sites immediately.
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<h3 id="maintenance-updates" class="wp-block-heading">Security updates</h3>
<p class="wp-block-paragraph">This release features several security fixes. Because this is a security release, <strong>it is recommended that you update your sites immediately.</strong></p>
<p class="wp-block-paragraph">The security team would like to thank the following people for <a href="https://hackerone.com/wordpress?type=team">responsibly reporting vulnerabilities</a>, and allowing them to be fixed in this release:</p>
<ul class="wp-block-list"> <li>A Blind SSRF issue reported by <a href="https://hackerone.com/sibwtf">sibwtf</a>, and subsequently by several other researchers while the fix was being worked on</li>
<li>A PoP-chain weakness in the HTML API and Block Registry reported by <a href="https://github.com/hackerlo2003">Phat RiO</a></li>
<li>A regex DoS weakness in numeric character references reported by Dennis Snell of the WordPress Security Team</li>
<li>A stored XSS in nav menus reported by <a href="https://x.com/Savphill">Phill Savage</a></li>
<li>An AJAX <code>query-attachments</code> authorization bypass reported by <a href="https://www.vitalysim.com/">Vitaly Simonovich</a></li>
<li>A stored XSS via the <code>data-wp-bind</code> directive reported by <a href="https://profiles.wordpress.org/kaminuma/">kaminuma</a></li>
<li>An XSS that allows overridding client-side templates in the admin area reported by <a href="https://hackerone.com/amosec">Asaf Mozes</a></li>
<li>A PclZip path traversal issue reported independently by <a href="https://profiles.wordpress.org/francescocarlucci/">Francesco Carlucci</a> and <a href="https://profiles.wordpress.org/kaminuma/">kaminuma</a></li>
<li>An XXE in the external getID3 library reported by <a href="https://profiles.wordpress.org/regex33/">Youssef Achtatal</a></li> </ul>
<p class="wp-block-paragraph">The WordPress security team have worked with the maintainer of the external getID3 library, James Heinrich, to coordinate a fix to getID3. A new version of getID3 <a href="https://github.com/JamesHeinrich/getID3/releases">is available here</a>.<br>As a courtesy, these fixes are being backported, where necessary, to all branches eligible to receive security fixes (currently through 4.7). As a reminder, <strong>only the most recent version of WordPress is actively supported</strong>.</p>
This release features 2 security fixes. Because this is a security release, it is recommended that you update your sites immediately.
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<h3 class="wp-block-heading" id="maintenance-updates">Security updates</h3>
<p>This release features 2 security fixes. Because this is a security release, <strong>it is recommended that you update your sites immediately.</strong></p>
<p>The security team would like to thank the following people for <a href="https://hackerone.com/wordpress?type=team">responsibly reporting vulnerabilities</a>, and allowing them to be fixed in this release:</p>
<ul class="wp-block-list"> <li>A data exposure issue where authenticated users could access some restricted content. Independently reported by <a href="https://hackerone.com/mnelson4">Mike Nelson</a>, <a href="https://hackerone.com/hurayraiit">Abu Hurayra</a>, <a href="https://profiles.wordpress.org/timothyblynjacobs/">Timothy Jacobs</a> and <a href="https://profiles.wordpress.org/peterwilsoncc/">Peter Wilson</a>.</li>
<li>A cross-site scripting (XSS) vulnerability requiring an authenticated role that affects the nav menus. Reported by <a href="https://x.com/Savphill">Phill Savage</a>.</li> </ul>
<p>As a courtesy to users on older branches of WordPress, these fixes are available in branches of WordPress going back to WordPress 4.7.</p>
_Sourced from WordPress.org Documentation._
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<p>This minor release includes an update to the root security certificate bundle. Please refer to the <a href="https://wordpress.org/news/2025/08/maintenance-releases-for-wordpress-branches-4-7-to-6-7/">release announcement</a> for further info.</p>
_Sourced from WordPress.org Documentation._
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<p>This release was led by <a href="https://profiles.wordpress.org/hellofromTonya">Tonya Mork</a> and <a href="https://profiles.wordpress.org/vcanales/">Vicente Canales</a>, with <a href="https://profiles.wordpress.org/jorbin/">Aaron Jorbin</a>.<br>WordPress 6.6.2 is a short-cycle maintenance release that features <a href="https://core.trac.wordpress.org/query?status=closed&id=!61982&milestone=6.6.2&group=status&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&col=keywords&order=id">15 bug fixes in Core</a> and <a href="https://core.trac.wordpress.org/ticket/61982#comment:5">11 bug fixes for the Block Editor</a>, including fixes related to CSS Specificity producing unexpected changes with some themes. </p>
<p>You can review a summary of the maintenance updates in this release by reading the <a href="https://make.wordpress.org/core/2024/09/04/wordpress-6-6-2-rc1-is-now-available/">Release Candidate announcement</a>.</p>
<p>For more information, <a href="https://core.trac.wordpress.org/query?status=closed&resolution=fixed&milestone=6.6.2&order=priority">browse the full list of changes on Trac</a>.</p>
_Sourced from WordPress.org Documentation._
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<p>The 6.6.1 release was led by <a href="https://profiles.wordpress.org/hellofromTonya">Tonya Mork</a> and <a href="https://profiles.wordpress.org/ellatrix/">Ella</a>.<br>WordPress 6.6.1 is a short-cycle maintenance release that features es <a href="https://core.trac.wordpress.org/query?status=closed&id=!61692&milestone=6.6.1&group=status&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&col=keywords&order=priority">7 bug fixes in Core</a> and <a href="https://core.trac.wordpress.org/ticket/61692">9 bug fixes for the Block Editor</a>.<br>You can review a summary of the maintenance updates in this release by reading the <a href="https://make.wordpress.org/core/2024/07/18/wordpress-6-6-1-rc1-is-now-available/">Release Candidate announcement</a>.</p>
<p><strong>Thank you to everyone who contributed to WordPress 6.6.1</strong></p>
<p><a href="https://profiles.wordpress.org/jorbin">Aaron Jorbin</a>, <a href="https://profiles.wordpress.org/aaronrobertshaw">Aaron Robertshaw</a>, <a href="https://profiles.wordpress.org/wildworks">Aki Hamano</a>, <a href="https://profiles.wordpress.org/amitraj2203">Amit Raj</a>, <a href="https://profiles.wordpress.org/afercia">Andrea Fercia</a>, <a href="https://profiles.wordpress.org/andrewserong">Andrew Serong</a>, <a href="https://profiles.wordpress.org/annezazu">annezazu</a>, <a href="https://profiles.wordpress.org/ambrosiawt">Art Smith</a>, <a href="https://profiles.wordpress.org/bgardner">Brian Gardner</a>, <a href="https://profiles.wordpress.org/poena">Carolina Nymark</a>, <a href="https://profiles.wordpress.org/cbirdsong">cbirdsong</a>, <a href="https://profiles.wordpress.org/butterflymedia">Ciprian</a>, <a href="https://profiles.wordpress.org/clarktbt">Clark</a>, <a href="https://profiles.wordpress.org/courane01">Courtney Robertson</a>, <a href="https://profiles.wordpress.org/talldanwp">Daniel Richards</a>, <a href="https://profiles.wordpress.org/davidbaumwald">David Baumwald</a>, <a href="https://profiles.wordpress.org/dmsnell">Dennis Snell</a>, <a href="https://profiles.wordpress.org/dd32">Dion Hulse</a>, <a href="https://profiles.wordpress.org/ellatrix">Ella</a>, <a href="https://profiles.wordpress.org/annubis">Eric-Oliver Mächler</a>, <a href="https://profiles.wordpress.org/fabiankaegy">Fabian Kägy</a>, <a href="https://profiles.wordpress.org/mamaduka">George Mamadashvili</a>, <a href="https://profiles.wordpress.org/jsnajdr">Jarda Snajdr</a>, <a href="https://profiles.wordpress.org/audrasjb">Jb Audras</a>, <a href="https://profiles.wordpress.org/joedolson">Joe Dolson</a>, <a href="https://profiles.wordpress.org/joen">Joen A.</a>, <a href="https://profiles.wordpress.org/jonsurrell">Jon Surrell</a>, <a href="https://profiles.wordpress.org/mciampini">Marco Ciampini</a>, <a href="https://profiles.wordpress.org/santosguillamot">Mario Santos</a>, <a href="https://profiles.wordpress.org/markhowellsmead">Mark Howells-Mead</a>, <a href="https://profiles.wordpress.org/mukesh27%20">Mukesh Panchal</a>, <a href="https://profiles.wordpress.org/neotrope">neotrope</a>, <a href="https://profiles.wordpress.org/swissspidy">Pascal Birchler</a>, <a href="https://profiles.wordpress.org/pbiron">Paul Biron</a>, <a href="https://profiles.wordpress.org/ramonopoly">ramonopoly</a>, <a href="https://profiles.wordpress.org/raquelandefeld">Raquel</a>, <a href="https://profiles.wordpress.org/youknowriad">Riad Benguella</a>, <a href="https://profiles.wordpress.org/richtabor">Rich Tabor</a>, <a href="https://profiles.wordpress.org/noisysocks">Robert Anderson</a>, <a href="https://profiles.wordpress.org/SergeyBiryukov">Sergey Biryukov</a>, <a href="https://profiles.wordpress.org/sourav08">Sourav Pahwa</a>, <a href="https://profiles.wordpress.org/sabernhardt">Stephen Bernhardt</a>, <a href="https://profiles.wordpress.org/sunil25393">SunilPrajapati</a>, <a href="https://profiles.wordpress.org/hellofromTonya">Tonya Mork</a>, <a href="https://profiles.wordpress.org/up1512001">up1512001</a></p>
<p>For more information, <a href="https://core.trac.wordpress.org/query?status=closed&resolution=fixed&milestone=6.6.1&order=priority">browse the full list of changes on Trac</a>.</p>
Version notes available on WordPress.org Documentation .
Version notes available on WordPress.org Documentation.
Version notes available on WordPress.org Documentation .
Version notes available on WordPress.org Documentation.
The security team would like to thank the following people for responsibly reporting vulnerabilities , and allowing them to be fixed in this release:
Sourced from WordPress.org Documentation.
This release features one security fix. Because this is a security release, it is recommended that you update your sites immediately.
The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:
Version notes available on WordPress.org Documentation .
Version notes available on WordPress.org Documentation.
One column per quarter.