NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
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:
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>
Your coding agent can read these notes before it upgrades. Set up the MCP server →
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>
This release features three security fixes. Because this is a security release, it is recommended that you update your sites immediately. This minor r…
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 three security fixes. Because this is a security release, <strong>it is recommended that you update your sites immediately. </strong>This minor release also includes <a href="https://core.trac.wordpress.org/query?component=!Build%2FTest+Tools&milestone=6.5.5&col=id&col=summary&col=owner&col=type&col=status&col=priority&col=component&order=priority">3 bug fixes</a> in Core.</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 cross-site scripting (XSS) vulnerability affecting the HTML API reported by Dennis Snell of the WordPress Core Team and Alex Concha and Grzegorz (Greg) Ziółkowski of the WordPress security team.</li>
<li>A cross-site scripting (XSS) vulnerability affecting the Template Part block reported independently by Rafie Muhammad of Patchstack and during a third party security audit.</li>
<li>A path traversal issue affecting sites hosted on Windows reported independently by Rafie M & Edouard L of Patchstack, David Fifield, <a href="https://hackerone.com/x89">x89</a>, <a href="https://hackerone.com/apple502j">apple502j</a>, and <a href="https://hackerone.com/mishre">mishre</a>.</li> </ul>
_Sourced from WordPress.org Documentation._
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<p>The 6.5.4 release was led by <a href="https://profiles.wordpress.org/hellofromtonya/">@hellofromtonya</a>, <a href="https://profiles.wordpress.org/costdev/">@costdev</a>, and <a href="https://profiles.wordpress.org/jorbin/">@jorbin</a><br>WordPress 6.5.4 is a short-cycle maintenance release that features <a href="https://core.trac.wordpress.org/query?status=closed&milestone=6.5.4&group=status&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&col=keywords&order=priority">5 bug fixes in Core</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/05/30/wordpress-6-5-4-rc1-is-now-available/">Release Candidate announcement</a>.</p>
<p><strong>Thank you to everyone who contributed to WordPress 6.5.3</strong><br><a href="https://profiles.wordpress.org/jorbin%22">Aaron Jorbin</a>, <a href="https://profiles.wordpress.org/adrianduffell">adrianduffell</a>, <a href="https://profiles.wordpress.org/azaozz">Andrew Ozz</a>, <a href="https://profiles.wordpress.org/afragen">Andy Fragen</a>, <a href="https://profiles.wordpress.org/beaulebens">Beau Lebens</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/costdev">Colin Stewart</a>, <a href="https://profiles.wordpress.org/nerrad">Darren Ethier (nerrad)</a>, <a href="https://profiles.wordpress.org/davidbaumwald/">David Baumwald</a>, <a href="https://profiles.wordpress.org/lopo">Enrico Battocchi</a>, <a href="https://profiles.wordpress.org/johnjamesjacoby">John James Jacoby</a>, <a href="https://profiles.wordpress.org/johnbillion">John Blackbourn</a>, <a href="https://profiles.wordpress.org/desrosj">Jonathan Desrosiers</a>, <a href="https://profiles.wordpress.org/kevinwhoffman">Kevin Hoffman</a>, <a href="https://profiles.wordpress.org/louiswol94">Louis Wolmarans</a>, <a href="https://profiles.wordpress.org/hmbashar">Md Abul Bashar</a>, <a href="https://profiles.wordpress.org/illuminea">Miriam Schwab</a>, <a href="https://profiles.wordpress.org/mukesh27">Mukesh Panchal</a>, <a href="https://profiles.wordpress.org/narenin">Narendra Sishodiya</a>, <a href="https://profiles.wordpress.org/swissspidy">Pascal Birchler</a>, <a href="https://profiles.wordpress.org/peterwilsoncc">Peter Wilson</a>, <a href="https://profiles.wordpress.org/pooja1210">Pooja N Muchandikar</a>, <a href="https://profiles.wordpress.org/mikachan">Sarah Norris</a>, <a href="https://profiles.wordpress.org/coffee2code/">Scott Reilly</a>, <a href="https://profiles.wordpress.org/smub">Syed Balkhi</a>, <a href="https://profiles.wordpress.org/hellofromTonya">Tonya Mork</a></p>
<p>For more information, <a href="https://core.trac.wordpress.org/query?status=closed&resolution=fixed&milestone=6.5.4&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.
This security and maintenance release features 2 bug fixes on Core , 12 bug fixes for the Block Editor , and 1 security fix:
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 security and maintenance release features <a href="https://core.trac.wordpress.org/query?status=closed&id=!60398&milestone=6.5.1&group=status&order=priority">2 bug fixes on Core</a>, <a href="https://github.com/WordPress/gutenberg/pull/60577">12 bug fixes for the Block Editor</a>, and 1 security fix:</p>
<ul> <li>A cross-site scripting (XSS) vulnerability affecting the Avatar block type; reported by <a href="https://johnblackbourn.com/">John Blackbourn</a> of the WordPress security team. Many thanks to <a href="https://twitter.com/stealthcopter">Mat Rollings</a> for assisting with the research.</li> </ul>
<p>The earliest release requiring patching was WordPress 6.1.</p>
<p><strong>Thank you to everyone who contributed to WordPress 6.5.2</strong>: <a href="https://profiles.wordpress.org/wildworks">Aki Hamano</a>, <a href="https://profiles.wordpress.org/andraganescu">Andrei Draganescu</a>, <a href="https://profiles.wordpress.org/artemiosans">Artemio Morales</a>, <a href="https://profiles.wordpress.org/iCaleb">Caleb Burks</a>, <a href="https://profiles.wordpress.org/colind">colind</a>, <a href="https://profiles.wordpress.org/talldanwp">Daniel Richards</a>, <a href="https://profiles.wordpress.org/ocean90">Dominik Schilling</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/gziolo">Greg Ziółkowski</a>, <a href="https://profiles.wordpress.org/isabel_brison">Isabel Brison</a>, <a href="https://profiles.wordpress.org/audrasjb">Jb Audras</a>, <a href="https://profiles.wordpress.org/joemcgill">Joe McGill</a>, <a href="https://profiles.wordpress.org/johnbillion">John Blackbourn</a>, <a href="https://profiles.wordpress.org/desrosj">Jonathan Desrosiers</a>, <a href="https://profiles.wordpress.org/thelovekesh">Lovekesh Kumar</a>, <a href="https://profiles.wordpress.org/mmaattiiaass">Matias Benedetto</a>, <a href="https://profiles.wordpress.org/mukesh27">Mukesh Panchal</a>, <a href="https://profiles.wordpress.org/swissspidy">Pascal Birchler</a>, <a href="https://profiles.wordpress.org/peterwilsoncc">Peter Wilson</a>, <a href="https://profiles.wordpress.org/sean212">Sean Fisher</a>, and <a href="https://profiles.wordpress.org/SergeyBiryukov">Sergey Biryukov</a>.</p>
<p>This release was led by <a href="https://profiles.wordpress.org/johnbillion/">John Blackbourn</a>, <a href="https://profiles.wordpress.org/isabel_brison/">Isabel Brison</a>, and <a href="https://github.com/sponsors/aaronjorbin/">Aaron Jorbin</a>.</p>
<p>For more information, <a href="https://core.trac.wordpress.org/query?status=closed&resolution=fixed&milestone=6.4.3&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.
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:
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 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:
_Version notes available on WordPress.org Documentation._
Version notes available on WordPress.org Documentation.
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>
This release features three security fixes. Because this is a security release, it is recommended that you update your sites immediately. This minor r…
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 three security fixes. Because this is a security release, <strong>it is recommended that you update your sites immediately. </strong>This minor release also includes <a href="https://core.trac.wordpress.org/query?component=!Build%2FTest+Tools&milestone=6.5.5&col=id&col=summary&col=owner&col=type&col=status&col=priority&col=component&order=priority">3 bug fixes</a> in Core.</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 cross-site scripting (XSS) vulnerability affecting the HTML API reported by Dennis Snell of the WordPress Core Team and Alex Concha and Grzegorz (Greg) Ziółkowski of the WordPress security team.</li>
<li>A cross-site scripting (XSS) vulnerability affecting the Template Part block reported independently by Rafie Muhammad of Patchstack and during a third party security audit.</li>
<li>A path traversal issue affecting sites hosted on Windows reported independently by Rafie M & Edouard L of Patchstack, David Fifield, <a href="https://hackerone.com/x89">x89</a>, <a href="https://hackerone.com/apple502j">apple502j</a>, and <a href="https://hackerone.com/mishre">mishre</a>.</li> </ul>
WordPress 6.5.1 includes 1 security fix:
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<h3 class="wp-block-heading" id="maintenance-updates">Security updates</h3>
<p>WordPress 6.5.1 includes 1 security fix: </p>
<ul> <li>A cross-site scripting (XSS) vulnerability affecting the Avatar block type; reported by <a href="https://johnblackbourn.com/">John Blackbourn</a> of the WordPress security team. Many thanks to <a href="https://twitter.com/stealthcopter">Mat Rollings</a> for assisting with the research.</li> </ul>
<p>The earliest release requiring patching was WordPress 6.1.</p>
<p><strong>Thank you to everyone who contributed to this version.</strong> For more information, <a href="https://core.trac.wordpress.org/query?status=closed&resolution=fixed&milestone=6.4.3&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.
_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 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:
_Version notes available on WordPress.org Documentation._
Version notes available on WordPress.org Documentation.
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>
This release features three security fixes. Because this is a security release, it is recommended that you update your sites immediately. This minor r…
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 three security fixes. Because this is a security release, <strong>it is recommended that you update your sites immediately. </strong>This minor release also includes <a href="https://core.trac.wordpress.org/query?component=!Build%2FTest+Tools&milestone=6.5.5&col=id&col=summary&col=owner&col=type&col=status&col=priority&col=component&order=priority">3 bug fixes</a> in Core.</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 cross-site scripting (XSS) vulnerability affecting the HTML API reported by Dennis Snell of the WordPress Core Team and Alex Concha and Grzegorz (Greg) Ziółkowski of the WordPress security team.</li>
<li>A cross-site scripting (XSS) vulnerability affecting the Template Part block reported independently by Rafie Muhammad of Patchstack and during a third party security audit.</li>
<li>A path traversal issue affecting sites hosted on Windows reported independently by Rafie M & Edouard L of Patchstack, David Fifield, <a href="https://hackerone.com/x89">x89</a>, <a href="https://hackerone.com/apple502j">apple502j</a>, and <a href="https://hackerone.com/mishre">mishre</a>.</li> </ul>
WordPress 6.5.1 includes 1 security fix:
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<h3 class="wp-block-heading" id="maintenance-updates">Security updates</h3>
<p>WordPress 6.5.1 includes 1 security fix: </p>
<ul> <li>A cross-site scripting (XSS) vulnerability affecting the Avatar block type; reported by <a href="https://johnblackbourn.com/">John Blackbourn</a> of the WordPress security team. Many thanks to <a href="https://twitter.com/stealthcopter">Mat Rollings</a> for assisting with the research.</li> </ul>
<p>The earliest release requiring patching was WordPress 6.1.</p>
<p><strong>Thank you to everyone who contributed to this version.</strong> For more information, <a href="https://core.trac.wordpress.org/query?status=closed&resolution=fixed&milestone=6.4.3&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.
This security and maintenance release features 19 bug fixes on Core , 22 bug fixes for the Block Editor, and 8 security fixes.
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading" id="summary">Summary</h2>
<h3 class="wp-block-heading" id="maintenance-updates">Maintenance updates</h3>
<p>This security and maintenance release features <a href="https://core.trac.wordpress.org/query?milestone=6.3.2&group=component&col=id&col=summary&col=milestone&col=owner&col=type&col=status&col=priority&order=priority">19 bug fixes on Core</a>, 22 bug fixes for the Block Editor, and 8 security fixes.</p>
<p>This is a short-cycle release. You can review a summary of the maintenance updates in this release by reading the <a href="https://make.wordpress.org/core/2023/10/06/wordpress-6-3-2-rc1-is-now-available/">Release Candidate announcement</a>.</p>
<h3 class="wp-block-heading">Security updates</h3>
<p>The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:</p>
<ul> <li>Marc Montpas of Automattic for finding a potential disclosure of user email addresses.</li>
<li>Marc Montpas of Automattic for finding an RCE POP Chains vulnerability.</li>
<li>Rafie Muhammad and Edouard L of <a href="https://patchstack.com/">Patchstack</a> along with a WordPress commissioned third-party audit for each independently identifying a XSS issue in the post link navigation block.</li>
<li><a href="https://www.linkedin.com/in/audrasjb/">Jb Audras</a> of the WordPress Security Team and Rafie Muhammad of <a href="https://patchstack.com/">Patchstack</a> for each independently discovering an issue where comments on private posts could be leaked to other users.</li>
<li><a href="https://hackerone.com/jamesgol?type=user">James Golovich</a> and <a href="https://hackerone.com/whitecybersec?type=user">WhiteCyberSec</a> for each independently identifying a way for logged in user to execute any shortcode.</li>
<li><a href="https://fb.com/zino.abdrahim">mascara7784</a> for identifying a XSS vulnerability in the application password screen.</li>
<li><a href="https://profiles.wordpress.org/jorgefilipecosta/">Jorge Costa</a> of the WordPress Core Team for identifying XSS vulnerability in the footnotes block.</li>
<li><a href="https://hackerone.com/s5s">s5s</a> and <a href="https://hackerone.com/raouf_maklouf">raouf_maklouf</a> for independently identifying a cache poisoning DoS vulnerability.</li> </ul>
_Sourced from WordPress.org Documentation._
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading" id="summary">Summary</h2>
<h3 class="wp-block-heading" id="maintenance-updates">Maintenance updates</h3>
<p>This minor release features <a href="https://core.trac.wordpress.org/query?status=closed&milestone=6.3.1&group=status&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&col=keywords&order=priority">4 bug fixes in Core</a> and <a href="https://github.com/orgs/WordPress/projects/103/">6 bug fixes for the block editor</a>. You can review a summary of the maintenance updates in this release by reading the <a href="https://make.wordpress.org/core/2023/08/23/wordpress-6-3-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>
This release features three security fixes. Because this is a security release, it is recommended that you update your sites immediately. This minor r…
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 three security fixes. Because this is a security release, <strong>it is recommended that you update your sites immediately. </strong>This minor release also includes <a href="https://core.trac.wordpress.org/query?component=!Build%2FTest+Tools&milestone=6.5.5&col=id&col=summary&col=owner&col=type&col=status&col=priority&col=component&order=priority">3 bug fixes</a> in Core.</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 cross-site scripting (XSS) vulnerability affecting the HTML API reported by Dennis Snell of the WordPress Core Team and Alex Concha and Grzegorz (Greg) Ziółkowski of the WordPress security team.</li>
<li>A cross-site scripting (XSS) vulnerability affecting the Template Part block reported independently by Rafie Muhammad of Patchstack and during a third party security audit.</li>
<li>A path traversal issue affecting sites hosted on Windows reported independently by Rafie M & Edouard L of Patchstack, David Fifield, <a href="https://hackerone.com/x89">x89</a>, <a href="https://hackerone.com/apple502j">apple502j</a>, and <a href="https://hackerone.com/mishre">mishre</a>.</li> </ul>
WordPress 6.5.1 includes 1 security fix:
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading">Summary</h2>
<h3 class="wp-block-heading" id="maintenance-updates">Security updates</h3>
<p>WordPress 6.5.1 includes 1 security fix: </p>
<ul> <li>A cross-site scripting (XSS) vulnerability affecting the Avatar block type; reported by <a href="https://johnblackbourn.com/">John Blackbourn</a> of the WordPress security team. Many thanks to <a href="https://twitter.com/stealthcopter">Mat Rollings</a> for assisting with the research.</li> </ul>
<p>The earliest release requiring patching was WordPress 6.1.</p>
<p><strong>Thank you to everyone who contributed to this version.</strong> For more information, <a href="https://core.trac.wordpress.org/query?status=closed&resolution=fixed&milestone=6.4.3&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.
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" id="summary">Summary</h2>
<p>This is a short-cycle release. You can review a summary of the maintenance updates in this release by reading the <a href="https://make.wordpress.org/core/2023/10/06/wordpress-6-3-2-rc1-is-now-available/">Release Candidate announcement</a>.</p>
<h3 class="wp-block-heading">Security updates</h3>
<p>The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release:</p>
<ul> <li>Marc Montpas of Automattic for finding a potential disclosure of user email addresses.</li>
<li>Marc Montpas of Automattic for finding an RCE POP Chains vulnerability.</li>
<li>Rafie Muhammad and Edouard L of <a href="https://patchstack.com/">Patchstack</a> along with a WordPress commissioned third-party audit for each independently identifying a XSS issue in the post link navigation block.</li>
<li><a href="https://www.linkedin.com/in/audrasjb/">Jb Audras</a> of the WordPress Security Team and Rafie Muhammad of <a href="https://patchstack.com/">Patchstack</a> for each independently discovering an issue where comments on private posts could be leaked to other users.</li>
<li><a href="https://hackerone.com/jamesgol?type=user">James Golovich</a> and <a href="https://hackerone.com/whitecybersec?type=user">WhiteCyberSec</a> for each independently identifying a way for logged in user to execute any shortcode.</li>
<li><a href="https://fb.com/zino.abdrahim">mascara7784</a> for identifying a XSS vulnerability in the application password screen.</li>
<li><a href="https://profiles.wordpress.org/jorgefilipecosta/">Jorge Costa</a> of the WordPress Core Team for identifying XSS vulnerability in the footnotes block.</li>
<li><a href="https://hackerone.com/s5s">s5s</a> and <a href="https://hackerone.com/raouf_maklouf">raouf_maklouf</a> for independently identifying a cache poisoning DoS vulnerability.</li> </ul>
The 6.2.2 minor release addresses 1 bug and 1 security issue. Because this is a security release, it is recommended that you update your sites immedia…
Sourced from WordPress.org Documentation.
<h2 class="wp-block-heading" id="summary">Summary</h2>
<p>The 6.2.2 minor release addresses <a href="https://core.trac.wordpress.org/query?milestone=6.2.2&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&order=priority">1 bug</a> and 1 security issue. Because this is a security release, it is recommended that you update your sites immediately. All versions since WordPress 5.9 have also been updated.</p>
<h3 class="wp-block-heading">Security updates</h3>
<p>The security team would like to thank the following people for responsibly reporting vulnerabilities and allowing them to be fixed in this release. </p>
<ul> <li>Block themes parsing shortcodes in user-generated data; thanks to Liam Gladdy of<a href="https://wpengine.com/"> WP Engine</a> for reporting this issue.</li> </ul>
<p>The issue above was originally patched in the 6.2.1 release, but needed further hardening here in 6.2.2. The Core team is thankful for the community in their response to 6.2.1 and collaboration on finding the best path forward for proper resolution in 6.2.2.</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.
<h2 class="wp-block-heading" id="summary">Summary</h2>
<h3 class="wp-block-heading" id="maintenance-updates">Maintenance updates</h3>
<p>This minor release features <a href="https://core.trac.wordpress.org/query?milestone=6.2.1&group=component&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&order=priority">20 bug fixes in Core</a> and <a href="https://github.com/orgs/WordPress/projects/88">10 bug fixes for the block editor</a>. You can review a summary of the maintenance updates in this release by reading the <a href="https://make.wordpress.org/core/2023/05/09/wordpress-6-2-1-rc1-is-now-available/">Release Candidate announcement</a>.</p>
<h3 class="wp-block-heading">Security updates</h3>
<p>The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release.</p>
<ul> <li>Block themes parsing shortcodes in user generated data; thanks to Liam Gladdy of <a href="https://wpengine.com/">WP Engine</a> for reporting this issue</li>
<li>A CSRF issue updating attachment thumbnails; reported by <a href="https://johnblackbourn.com/">John Blackbourn</a> of the WordPress security team</li>
<li>A flaw allowing XSS via open embed auto discovery; reported independently by Jakub Żoczek of <a href="https://research.securitum.com/">Securitum</a> and during a third party security audit</li>
<li>Bypassing of KSES sanitization in block attributes for low privileged users; discovered during a third party security audit.</li>
<li>A path traversal issue via translation files; reported independently by Ramuel Gall and during a third party security audit.</li> </ul>
_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.
<h2 class="wp-block-heading">Summary</h2>
<h3 class="wp-block-heading">Security updates</h3>
<p class="wp-block-paragraph">This release features one security fix. 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 stored XSS on the Comments administration page, exploitable via pending comments, reported by <a href="https://trailofbits.com/">Thomas Chauchefoin at Trail of Bits</a></li>
<li>A DoS issue in the <code>WP_Http::make_absolute_url()</code> method, reported by Anthropic</li>
<li>A weakness allowing Author role users to sticky posts, reported by Anthropic</li>
<li>Unauthenticated disclosure of comments on private & unpublished posts, reported by <a href="https://patchstack.com/">Ananda Dhakal from Patchstack</a></li>
<li>Imgur embeds are vulnerable to XSS, reported by <a href="https://jackfromeast.github.io/">Zhengyu Liu</a>, <a href="https://jesse-yang.com/">Jingcheng Yang</a>, and <a href="https://gvzhong.github.io/">Gavin Zhong</a></li>
<li>Forgeable parameters passed to the <code>{status}_{type}</code> hook can lead to action name collision, reported by Alex Concha of the WordPress security team</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>
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 one security fix. 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>An unauthenticated path traversal issue in page-template resolution leading to conditional remote code execution reported by Robert Ressl</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>An issue allowing a crafted URL to install and preview a theme from WordPress.org reported by Paulos Yibelo and pwn.ai</li>
<li>A stored cross-site scripting (XSS) issue in custom header images on some themes reported by Jeremy Felt of the WordPress Security Team</li>
<li>An information disclosure issue exposing the title of a private parent post reported by HDWSec</li>
<li>A multisite issue allowing a site administrator to network-activate a network-only plugin reported by Jesse McNeil</li>
<li>A Contributor+ arbitrary post overwrite issue reported by Anthropic</li>
<li>An authenticated path traversal issue in the REST API templates controller reported by Anthropic</li>
<li>An authorization issue allowing any authenticated user to reparent comments, including notes, reported by viridis</li>
<li>An XML-RPC issue allowing changeset posts to bypass the custom CSS capability check reported by Ben Bidner of the WordPress Security Team</li>
<li>A Contributor+ disclosure of draft and pending post slugs reported by hermanhms</li>
<li>An unauthenticated stored cross-site scripting (XSS) issue via paragraph formatting, subject to comment approval, reported by Rafie Muhammad (Awesome Motive, Inc.)</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>An authenticated Author+ remote code execution issue via malicious file upload on sites that use Imagick and Ghostscript reported by the team at pwn.ai</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 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 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>
One column per quarter.