What is CVE-2021-39203?

CVE-2021-39203 is a vulnerability in WordPress that allows authenticated users without permission to view private post types/data to bypass restrictions in the block editor.

What is the severity of CVE-2021-39203?

The severity of CVE-2021-39203 is medium with a CVSS score of 6.5.

How can I fix CVE-2021-39203 vulnerability in WordPress?

To fix the CVE-2021-39203 vulnerability in WordPress, consider upgrading to a version that includes the necessary security patches or follow the recommendations provided by WordPress.

Where can I find more information about CVE-2021-39203?

More information about CVE-2021-39203 can be found in the following references: - [GitHub Security Advisory](https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-qxvw-qxm9-qvg6) - [HackerOne Report](https://hackerone.com/reports/1225282)

Vulnerability/
CVE-2021-39203

medium

6.8

CWE

200

9/9/2021

5/8/2022

CVE-2021-39203: Infoleak

First published: Thu Sep 09 2021(Updated: )

WordPress is a free and open-source content management system written in PHP and paired with a MySQL or MariaDB database. In affected versions authenticated users who don't have permission to view private post types/data can bypass restrictions in the block editor under certain conditions. This affected WordPress 5.8 beta during the testing period. It's fixed in the final 5.8 release.

Credit: security-advisories@github.com

Affected Software	Affected Version	How to fix
WordPress WordPress	=5.8-beta1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is CVE-2021-39203?
CVE-2021-39203 is a vulnerability in WordPress that allows authenticated users without permission to view private post types/data to bypass restrictions in the block editor.
How does CVE-2021-39203 affect WordPress?
In affected versions, authenticated users who don't have permission to view private post types/data can bypass restrictions in the block editor under certain conditions.
What is the severity of CVE-2021-39203?
The severity of CVE-2021-39203 is medium with a CVSS score of 6.5.
How can I fix CVE-2021-39203 vulnerability in WordPress?
To fix the CVE-2021-39203 vulnerability in WordPress, consider upgrading to a version that includes the necessary security patches or follow the recommendations provided by WordPress.
Where can I find more information about CVE-2021-39203?
More information about CVE-2021-39203 can be found in the following references: - [GitHub Security Advisory](https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-qxvw-qxm9-qvg6) - [HackerOne Report](https://hackerone.com/reports/1225282)

agent/references
agent/severity
agent/weakness
agent/author
agent/type
agent/event
agent/description
agent/last-modified-date
agent/softwarecombine
agent/first-publish-date
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/wordpress
canonical/wordpress wordpress
version/wordpress wordpress/5.8-beta1

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.