You might have received an email that your WordPress website has been automatically updated. You can visit your WordPress website and update it manually if you haven’t. You can read about how you update your WordPress here.
WordPress 6.0.3 comes with a lot of security updates and security fixes. WordPress, therefore, recommends that you update your WordPress website immediately for your WordPress website to become fully secure.
When you update your WordPress website to 6.0.3, there are no breaking changes. You can quickly go ahead and update. That said, I strongly recommend you take a backup of your WordPress website just before you press update to have the newest backup available, should something happen. You can read how to take a backup of your WordPress website here.
As we come closer to November, we also come closer to a new major release: 6.1, which brings more design tools, a more refined template experience, more template options and much more.
Complete list of WordPress 6.0.3 update
- Stored XSS via wp-mail.php (post by email) – Toshitsugu Yoneyama of Mitsui Bussan Secure Directions, Inc. via JPCERT
- Open redirect in `wp_nonce_ays` – devrayn
- The sender’s email address is exposed in wp-mail.php – Toshitsugu Yoneyama of Mitsui Bussan Secure Directions, Inc. via JPCERT.
- Media Library – Reflected XSS via SQLi – Ben Bidner from the WordPress security team and Marc Montpas from Automattic independently discovered this issue
- CSRF in wp-trackback.php – Simon Scannell
- Stored XSS via the Customizer – Alex Concha from the WordPress security team
- Revert shared user instances introduced in 50790 – Alex Concha and Ben Bidner from the WordPress security team.
- Stored XSS in WordPress Core via Comment Editing – Third-party security audit and Alex Concha from the WordPress security team
- Data exposure via the REST Terms/Tags Endpoint – Than Taintor
- Content from multipart emails leaked – Thomas Kräftner
- SQL Injection due to improper sanitization in `WP_Date_Query` – Michael Mazzolini
- RSS Widget: Stored XSS issue – Third-party security audit
- Stored XSS in the search block – Alex Concha of the WP Security team
- Feature Image Block: XSS issue – Third-party security audit
- RSS Block: Stored XSS issue – Third-party security audit
- Fix widget block XSS – Third-party security audit