In affected versions of WordPress, some private posts, which were previously public, can result in unauthenticated disclosure under a specific set of conditions. This has been patched in version 5.4.1, along with all the previously affected versions via a minor release (5.3.3, 5.2.6, 5.1.5, 5.0.9, 4.9.14, 4.8.13, 4.7.17, 4.6.18, 4.5.21, 4.4.22, 4.3.23, 4.2.27, 4.1.30, 4.0.30, 3.9.31, 3.8.33, 3.7.33).
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Wordpress | Wordpress | * | 5.4.1 (excluding) |
| Wordpress | Ubuntu | bionic | * |
| Wordpress | Ubuntu | devel | * |
| Wordpress | Ubuntu | eoan | * |
| Wordpress | Ubuntu | esm-apps/bionic | * |
| Wordpress | Ubuntu | esm-apps/focal | * |
| Wordpress | Ubuntu | esm-apps/jammy | * |
| Wordpress | Ubuntu | esm-apps/noble | * |
| Wordpress | Ubuntu | esm-apps/xenial | * |
| Wordpress | Ubuntu | focal | * |
| Wordpress | Ubuntu | groovy | * |
| Wordpress | Ubuntu | hirsute | * |
| Wordpress | Ubuntu | impish | * |
| Wordpress | Ubuntu | jammy | * |
| Wordpress | Ubuntu | kinetic | * |
| Wordpress | Ubuntu | lunar | * |
| Wordpress | Ubuntu | mantic | * |
| Wordpress | Ubuntu | noble | * |
| Wordpress | Ubuntu | oracular | * |
| Wordpress | Ubuntu | trusty | * |
| Wordpress | Ubuntu | upstream | * |
| Wordpress | Ubuntu | xenial | * |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: