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.
_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>
Your coding agent can read these notes before it upgrades. Set up the MCP server →
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.
<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>
_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 maintenance release features <a href="https://core.trac.wordpress.org/query?milestone=6.1.1&order=priority">28 bug fixes in Core</a> and <a href="https://github.com/WordPress/gutenberg/commits/wp/6.1">18 bug fixes</a> for the Block Editor.</p>
<p>The following core tickets from Trac were fixed:</p>
<ul> <li>Canonical: Setting a <code>NOT EXISTS</code> tax query in <code>pre_get_posts</code> action triggers a fatal error in <code>wp-includes/canonical.php</code> (<a href="https://core.trac.wordpress.org/ticket/55955">#55955</a>)</li>
<li>Editor: Massive (potential) performance issues within <code>get_default_block_editor_settings</code> (<a href="https://core.trac.wordpress.org/ticket/56815">#56815</a>)</li>
<li>Editor: Padding within table cells ignored (<a href="https://core.trac.wordpress.org/ticket/56818">#56818</a>)</li>
<li>Editor: Creating taxonomy templates for specific terms are wrongly displayed as not found (<a href="https://core.trac.wordpress.org/ticket/56902">#56902</a>)</li>
<li>Editor: Separator colors defined using background within <code>theme.json</code> for style variations are ignored (<a href="https://core.trac.wordpress.org/ticket/56903">#56903</a>)</li>
<li>Editor: Avoid running unnecessary expensive logic around <code>theme.json</code> parsing for classic themes (<a href="https://core.trac.wordpress.org/ticket/56945">#56945</a>)</li>
<li>Editor: Unable to add blocks on WP 6.1 – “+” button in editor shows up only in certain condition (<a href="https://core.trac.wordpress.org/ticket/56955">#56955</a>)</li>
<li>Editor: Improve performance of the <code>WP_Theme_JSON</code> class (<a href="https://core.trac.wordpress.org/ticket/56974">#56974</a>)</li>
<li>Editor: Merge bugfixes from Gutenberg into Core for WP 6.1.1 (<a href="https://core.trac.wordpress.org/ticket/57038">#57038</a>)</li>
<li>Editor: Fluid typography fixes for 6.1.1 (<a href="https://core.trac.wordpress.org/ticket/57075">#57075</a>)</li>
<li>Formatting: Check that the Normalizer class exists in <code>remove_accents()</code> (<a href="https://core.trac.wordpress.org/ticket/56980">#56980</a>)</li>
<li>General: Update to <code>get_page_by_title</code> in 6.1 changes <code>WHERE</code> clause (<a href="https://core.trac.wordpress.org/ticket/56991">#56991</a>)</li>
<li>I18N: Fatal error when loading translations early due to a DB error with <code>WPLANG</code> set (<a href="https://core.trac.wordpress.org/ticket/57051">#57051</a>)</li>
<li>I18N: Always pass <code>$locale</code> to <code>load_textdomain()</code> if we know the locale (<a href="https://core.trac.wordpress.org/ticket/57060">#57060</a>)</li>
<li>Media: Featured Image bug in 6.0.3 (<a href="https://core.trac.wordpress.org/ticket/56855">#56855</a>)</li>
<li>Media: <code>decoding="async"</code> breaks my site (<a href="https://core.trac.wordpress.org/ticket/56969">#56969</a>)</li>
<li>Menus: WP 6.1-RC6: <code>menu-item-has-children</code> class is not being applied correctly (<a href="https://core.trac.wordpress.org/ticket/56946">#56946</a>)</li>
<li>Post, Post Types: WP 6.1 – <code>get_page_by_title(null)</code> returns a page (<a href="https://core.trac.wordpress.org/ticket/57039">#57039</a>)</li>
<li>Query: <code>WP_Query::the_post</code> causes a type warning when querying for ids, not full post objects (<a href="https://core.trac.wordpress.org/ticket/56948">#56948</a>)</li>
<li>Query: <code>WP_Query</code> caching discards <code>posts_fields</code> and <code>posts_clauses['fields']</code> filters. (<a href="https://core.trac.wordpress.org/ticket/57012">#57012</a>)</li>
<li>Text Changes: Replace instances of “Full site editing” with “Site editor” (<a href="https://core.trac.wordpress.org/ticket/57026">#57026</a>)</li>
<li>Themes: <code>register_block_core_template_part</code> does <code>WP_Query</code> even on themes that do not support it (<a href="https://core.trac.wordpress.org/ticket/56923">#56923</a>)</li>
<li>Themes: <code>WP_Theme_JSON_Resolver::get_user_data_from_wp_global_styles</code> call to <code>WP_Query</code> incorrect. (<a href="https://core.trac.wordpress.org/ticket/56900">#56900</a>)</li>
<li>Themes: Twenty Twenty-Three: visited state of button links use the incorrect text color (<a href="https://core.trac.wordpress.org/ticket/56928">#56928</a>)</li>
<li>Themes: Reduce usage of <code>wp_get_theme</code> (<a href="https://core.trac.wordpress.org/ticket/57057">#57057</a>)</li>
<li>Upgrade/Install: Updating plugins with WP6.1 creates <code>.maintenance</code> file and leaves it (<a href="https://core.trac.wordpress.org/ticket/56966">#56966</a>)</li>
<li>Upgrade/Install: An unupdated Version of Gutenberg Fatally breaks the site on WordPress 6.1 Autoupdate (<a href="https://core.trac.wordpress.org/ticket/56985">#56985</a>)</li>
<li>Users: <code>cache_users()</code> not defined when calling <code>get_user</code> without field parameter or using <code>all_with_meta</code> or <code>all</code> (<a href="https://core.trac.wordpress.org/ticket/56952">#56952</a>)</li> </ul>
<p>The following block editor issues from GitHub were fixed:</p>
<ul> <li>Post Featured Image: Fix height/scale overwriting border inline styles (<a href="https://github.com/WordPress/gutenberg/pull/44213">#44213</a>)</li>
<li>Fluid typography: add font size constraints (<a href="https://github.com/WordPress/gutenberg/pull/44993">#44993</a>)</li>
<li>Allow direct selection of nested Page List block by avoiding dual rendering within block (<a href="https://github.com/WordPress/gutenberg/pull/45143">#45143</a>)</li>
<li>Fix popover deprecations (<a href="https://github.com/WordPress/gutenberg/pull/45195">#45195</a>)</li>
<li>Components: Refactor <code>ColorPalette</code> tests to <code>@testing-library/react</code> (<a href="https://github.com/WordPress/gutenberg/pull/44108">#44108</a>)</li>
<li>Convert the <code>ColorPalette</code> component to TypeScript (<a href="https://github.com/WordPress/gutenberg/pull/44632">#44632</a>)</li>
<li>List v2: fix migration when nested list is invalid (<a href="https://github.com/WordPress/gutenberg/pull/44822">#44822</a>)</li>
<li>Link to <code>homeUrl</code> from site editor view menu. (<a href="https://github.com/WordPress/gutenberg/pull/45475">#45475</a>)</li>
<li>Table Block: Apply borders and padding on both front end and editor (<a href="https://github.com/WordPress/gutenberg/pull/45069">#45069</a>)</li>
<li>Change the order of the pseudo-states in the pseudo selectors array (<a href="https://github.com/WordPress/gutenberg/pull/45559">#45559</a>)</li>
<li>Do not look for block variants, if not supporting block-templates (<a href="https://github.com/WordPress/gutenberg/pull/45362">#45362</a>)</li>
<li>Restore the empty paragraph inserter (<a href="https://github.com/WordPress/gutenberg/pull/45542">#45542</a>)</li>
<li>Cover: Avoid content loss when the <code>templateLock</code> value is <code>all</code> or <code>contentOnly</code> (<a href="https://github.com/WordPress/gutenberg/pull/45632">#45632</a>)</li>
<li>List: disable nested list drop zone so dropping list items works (<a href="https://github.com/WordPress/gutenberg/pull/45321">#45321</a>)</li>
<li>Switch background color to text color on block separator (<a href="https://github.com/WordPress/gutenberg/pull/44943">#44943</a>)</li>
<li>[WP6.1.1] AutoComplete: Revert to <code>event.keyCode</code> to fix IME composition issue (<a href="https://github.com/WordPress/gutenberg/pull/45704">#45704</a>)</li>
<li>[WP6.1.1] FormTokenField: Revert to <code>event.keyCode</code> to fix IME composition issue (<a href="https://github.com/WordPress/gutenberg/pull/45703">#45703</a>)</li>
<li>Fluid typography: adjust font size min and max rules (<a href="https://github.com/WordPress/gutenberg/pull/45536">#45536</a>)</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 Editor+ stored cross-site scripting (XSS) issue in the personal data erasure requests screen reported by Anthropic</li>
<li>A Contributor+ stored cross-site scripting (XSS) issue via whitespace in block delimiters reported by Rafie Muhammad (Awesome Motive, Inc.)</li>
<li>An information disclosure issue exposing unpublished Customizer changes to unauthenticated visitors reported by Antonio Lorensius Silaban</li>
<li>A hardening fix for unescaped usernames on the multisite Network Users screens reported by Anthropic</li>
<li>A race condition during core updates that could lead to remote code execution reported by Umut Bayram</li>
<li>A Contributor+ stored cross-site scripting (XSS) issue in Customizer selective refresh reported by Rafie Muhammad (Awesome Motive, Inc.)</li>
<li>A Contributor+ stored cross-site scripting (XSS) issue in the labels of the Comments Pagination and Post Navigation Link blocks reported by Alex Concha of the WordPress Security Team</li>
<li>An update to the bundled root certificates due to the eMudhra revocation.</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 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>
_Version notes available on WordPress.org Documentation._
Version notes available on WordPress.org Documentation.
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>
_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.
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>
_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>
<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>
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">Security updates included in this release</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>Stored XSS via wp-mail.php (post by email) – Toshitsugu Yoneyama of Mitsui Bussan Secure Directions, Inc. via JPCERT</li>
<li>Open redirect in wp_nonce_ays – <a href="https://hackerone.com/devrayn">devrayn</a></li>
<li>Sender’s email address is exposed in wp-mail.php – Toshitsugu Yoneyama of Mitsui Bussan Secure Directions, Inc. via JPCERT</li>
<li>Media Library – Reflected XSS via SQLi – Ben Bidner from the WordPress security team and Marc Montpas from Automattic independently discovered this issue</li>
<li>CSRF in wp-trackback.php – Simon Scannell</li>
<li>Stored XSS via the Customizer – Alex Concha from the WordPress security team</li>
<li>Revert shared user instances introduced in <a href="https://core.trac.wordpress.org/changeset/50790">50790</a> – Alex Concha and Ben Bidner from the WordPress security team</li>
<li>Stored XSS in WordPress Core via Comment Editing – Third-party security audit and Alex Concha from the WordPress security team</li>
<li>Data exposure via the REST Terms/Tags Endpoint – Than Taintor</li>
<li>Content from multipart emails leaked – <a href="https://profiles.wordpress.org/kraftner">Thomas Kräftner</a></li>
<li>SQL Injection due to improper sanitization in WP_Date_Query – <a href="https://www.gold-network.ch">Michael Mazzolini</a></li>
<li>RSS Widget: Stored XSS issue – Third-party security audit</li>
<li>Stored XSS in the search block – Alex Concha of the WP Security team</li>
<li>Feature Image Block: XSS issue – Third-party security audit</li>
<li>RSS Block: Stored XSS issue – Third-party security audit</li>
<li>Fix widget block XSS – Third-party security audit</li> </ul>
Nothing published for this version
Nothing published for this version
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 Editor+ stored cross-site scripting (XSS) issue in the personal data erasure requests screen reported by Anthropic</li>
<li>A Contributor+ stored cross-site scripting (XSS) issue via whitespace in block delimiters reported by Rafie Muhammad (Awesome Motive, Inc.)</li>
<li>An information disclosure issue exposing unpublished Customizer changes to unauthenticated visitors reported by Antonio Lorensius Silaban</li>
<li>A hardening fix for unescaped usernames on the multisite Network Users screens reported by Anthropic</li>
<li>A race condition during core updates that could lead to remote code execution reported by Umut Bayram</li>
<li>A Contributor+ stored cross-site scripting (XSS) issue in Customizer selective refresh reported by Rafie Muhammad (Awesome Motive, Inc.)</li>
<li>A Contributor+ stored cross-site scripting (XSS) issue in the labels of the Comments Pagination and Post Navigation Link blocks reported by Alex Concha of the WordPress Security Team</li>
<li>An update to the bundled root certificates due to the eMudhra revocation.</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 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> </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>
_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>
_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>
<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.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
_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>
_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 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>
_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 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> </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 one security fix. 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 one security fix. 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 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>
_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>
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.
Nothing published for this version
One column per quarter.