First published: Fri Dec 27 2019(Updated: )
In in wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php in WordPress 3.7 to 5.3.0, authenticated users who do not have the rights to publish a post are able to mark posts as sticky or unsticky via the REST API. For example, the contributor role does not have such rights, but this allowed them to bypass that. This has been patched in WordPress 5.3.1, along with all the previous WordPress versions from 3.7 to 5.3 via a minor release.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
debian/wordpress | 5.0.15+dfsg1-0+deb10u1 5.0.19+dfsg1-0+deb10u1 5.7.8+dfsg1-0+deb11u2 6.1.1+dfsg1-1 6.3.1+dfsg1-1 | |
WordPress WordPress | >=3.7<5.3.1 | |
Debian Debian Linux | =9.0 | |
Debian Debian Linux | =10.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-20043 is a vulnerability in WordPress 3.7 to 5.3.0 that allows authenticated users without the rights to publish a post to mark posts as sticky or unsticky via the REST API.
CVE-2019-20043 has a severity rating of 4.3, which is considered medium.
WordPress versions 3.7 to 5.3.0 are affected by CVE-2019-20043.
To fix CVE-2019-20043, update your WordPress installation to version 5.0.15+dfsg1-0+deb10u1, 5.0.19+dfsg1-0+deb10u1, 5.7.8+dfsg1-0+deb11u2, 6.1.1+dfsg1-1, or 6.3.1+dfsg1-1.
You can find more information about CVE-2019-20043 on the following references: [link1], [link2], [link3].