Vulnerabilities · 2019 · Wordpress
CVE-2019-20043
Wordpress vulnerability
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.
Affected products
Wordpress, Debian Linux. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Wordpress runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/ · Vendor Advisory
- core.trac.wordpress.org/changeset/46893/trunk · Patch
- github.com/WordPress/wordpress-develop/commit/1d1d5be7aa94608c04516cac4238e8c22b93c1d9 · Third Party Advisory
- github.com/WordPress/wordpress-develop/security/advisories/GHSA-g7rg-hchx-c2gw · Third Party Advisory
- seclists.org/bugtraq/2020/Jan/8 · Third Party Advisory
- wpvulndb.com/vulnerabilities/9973 · Third Party Advisory
- www.debian.org/security/2020/dsa-4599 · Third Party Advisory
- www.debian.org/security/2020/dsa-4677 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2019-20043
- cve.org/CVERecord?id=CVE-2019-20043
More vulnerabilities in Wordpress products
CVE-2024-31211CVE-2024-31210CVE-2024-8914CVE-2024-4439CVE-2023-39999CVE-2023-38000CVE-2023-22622CVE-2023-5561All 407
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.