{"id":16562,"date":"2023-12-06T17:03:48","date_gmt":"2023-12-06T17:03:48","guid":{"rendered":"https:\/\/wordpress.org\/news\/?p=16562"},"modified":"2023-12-06T17:03:48","modified_gmt":"2023-12-06T17:03:48","slug":"wordpress-6-4-2-maintenance-security-release","status":"publish","type":"post","link":"https:\/\/wordpress.org\/news\/2023\/12\/wordpress-6-4-2-maintenance-security-release\/","title":{"rendered":"WordPress 6.4.2 Maintenance & Security Release"},"content":{"rendered":"\n
This minor release features 7 bug fixes<\/a> in Core. The fixes include a bug fix for an issue causing stylesheet and theme directories to sometimes return incorrect results.<\/p>\n\n\n\n This release also features one security fix. Because this is a security release, it is recommended that you update your sites immediately<\/strong>.<\/strong><\/p>\n\n\n\n You can download WordPress 6.4.2 from WordPress.org<\/a>, or visit your WordPress Dashboard, click \u201cUpdates\u201d, and then click \u201cUpdate Now\u201d. If you have sites that support automatic background updates, the update process will begin automatically.<\/p>\n\n\n\n WordPress 6.4.2 is a short-cycle release. The next major release will be version 6.5 released in early 2024.<\/p>\n\n\n\n For more information on this release, please visit the HelpHub site<\/a>.<\/p>\n\n\n\n The security team addressed the following vulnerability in this release.<\/p>\n\n\n\n To help the security team and WordPressers around the world, you are encouraged to responsibly report vulnerabilities<\/a>. This allows vulnerabilities to be fixed in future releases.<\/p>\n\n\n\n This release was led by Aaron Jorbin<\/a>.<\/p>\n\n\n\n WordPress 6.4.2 would not have been possible without the contributions of the following people. Their asynchronous coordination to deliver maintenance and security fixes into a stable release is a testament to the power and capability of the WordPress community.<\/p>\n\n\n\n Aaron Jorbin<\/a>, Aki Hamano<\/a>, Akira Tachibana<\/a>, Alex Concha<\/a>, Angela Jin<\/a>, Anton Vlasenko<\/a>, Barry<\/a>, bernhard-reiter<\/a>, Caleb Burks<\/a>, Corey Worrell<\/a>, crstauf<\/a>, Darren Ethier (nerrad)<\/a>, David Baumwald<\/a>, Dennis Snell<\/a>, Dion Hulse<\/a>, Erik<\/a>, Fabian Todt<\/a>, Felix Arntz<\/a>, H\u00e9ctor Prieto<\/a>, ironprogrammer<\/a>, Isabel Brison<\/a>, Jb Audras<\/a>, Jeffrey Paul<\/a>, Jessica Lyschik<\/a>, Joe McGill<\/a>, John Blackbourn<\/a>, Jonathan Desrosiers<\/a>, Kharis Sulistiyono<\/a>, Krupal Panchal<\/a>, Kylen Downs<\/a>, meta4<\/a>, Mike Schroder<\/a>, Mukesh Panchal<\/a>, partyfrikadelle<\/a>, Peter Wilson<\/a>, Pieterjan Deneys<\/a>, rawrly<\/a>, rebasaurus<\/a>, Sergey Biryukov<\/a>, Tonya Mork<\/a>, vortfu<\/a><\/p>\n\n\n\n To get involved in WordPress core development, head over to Trac, pick a ticket<\/a>, and join the conversation in the #core<\/a>. Need help? Check out the Core Contributor Handbook<\/a>.<\/p>\n\n\n\n As a final reminder, The WordPress Security Team will never email you requesting that you install a plugin or theme on your site, and will never ask for an administrator username and password. Please stay vigilant against phishing attacks<\/a>.<\/p>\n\n\n\n Thanks to @angelasjin<\/a> and @desrosj<\/a> for proofreading.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":" WordPress 6.4.2 is now available! This minor release features 7 bug fixes in Core. The fixes include a bug fix for an issue causing stylesheet and theme directories to sometimes return incorrect results. This release also features one security fix. Because this is a security release, it is recommended that you update your sites immediately. […]<\/p>\n","protected":false},"author":2738372,"featured_media":0,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"episode_type":"","audio_file":"","cover_image":"","cover_image_id":"","duration":"","filesize":"","date_recorded":"","explicit":"","block":"","filesize_raw":"","jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[14,15],"tags":[],"class_list":["post-16562","post","type-post","status-publish","format-standard","hentry","category-releases","category-security"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pZhYe-4j8","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts\/16562","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/users\/2738372"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/comments?post=16562"}],"version-history":[{"count":5,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts\/16562\/revisions"}],"predecessor-version":[{"id":16568,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts\/16562\/revisions\/16568"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/media?parent=16562"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/categories?post=16562"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/tags?post=16562"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Security updates included in this release<\/h2>\n\n\n\n
\n
Thank you to these WordPress contributors<\/h2>\n\n\n\n
How to contribute<\/h2>\n\n\n\n