{"id":"CVE-2019-20043","aliases":["DEBIAN-CVE-2019-20043","DSA-4599-1","EUVD-2019-10599","GHSA-g7rg-hchx-c2gw","GHSA-ppxh-5qq2-77g8","UBUNTU-CVE-2019-20043"],"status":"published","title":"WordPress before 5.3.1 allowed an unauthenticated user to make a post sticky through the REST API...","description":"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.","severity":{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","level":"medium","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-09","score":0.02475,"percentile":0.84666,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-269"],"published":"2019-12-27T07:14:16Z","modified":"2026-10-24T10:49:51Z","fixes":[{"ecosystem":"Debian:12","package":"wordpress","fixed_in":["5.3.2+dfsg1-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"wordpress","fixed_in":["5.3.2+dfsg1-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"wordpress","fixed_in":["5.3.2+dfsg1-1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:12","package":"wordpress","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.2+dfsg1-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"wordpress","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.2+dfsg1-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"wordpress","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.2+dfsg1-1"}]}]},{"source":"osv","ecosystem":"Debian:10","package":"wordpress","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.0.4+dfsg1-1+deb10u1"}]}],"versions":["5.0.4+dfsg1-1"],"bundled":18},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"wordpress","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.3+dfsg-1","4.3.1+dfsg-1","4.4+dfsg-1","4.4.1+dfsg-1","4.4.2+dfsg-1","4.4.2+dfsg-1ubuntu1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"wordpress","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.8.2+dfsg-2","4.8.3+dfsg-1","4.9.1+dfsg-1","4.9.2+dfsg-1","4.9.4+dfsg-1","4.9.5+dfsg1-1"]}],"products":[{"vendor":"debian","product":"debian_linux"},{"vendor":"wordpress","product":"wordpress"}],"references":[{"url":"https://wpvulndb.com/vulnerabilities/9973","tags":["x_refsource_MISC","x_transferred","Release Notes","Third Party Advisory","advisory","report"]},{"url":"https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/","tags":["x_refsource_MISC","x_transferred","Release Notes","Vendor Advisory","advisory","report"]},{"url":"https://core.trac.wordpress.org/changeset/46893/trunk","tags":["x_refsource_MISC","x_transferred","Patch","fix","report"]},{"url":"https://github.com/WordPress/wordpress-develop/commit/1d1d5be7aa94608c04516cac4238e8c22b93c1d9","tags":["x_refsource_MISC","x_transferred","Third Party Advisory","advisory","report"]},{"url":"https://seclists.org/bugtraq/2020/Jan/8","tags":["mailing-list","x_refsource_BUGTRAQ","x_transferred","Mailing List","Third Party Advisory","advisory"]},{"url":"https://www.debian.org/security/2020/dsa-4599","tags":["vendor-advisory","x_refsource_DEBIAN","x_transferred","Third Party Advisory","advisory"]},{"url":"https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-g7rg-hchx-c2gw","tags":["x_refsource_CONFIRM","x_transferred","Third Party Advisory","advisory"]},{"url":"https://www.debian.org/security/2020/dsa-4677","tags":["vendor-advisory","x_refsource_DEBIAN","x_transferred","Third Party Advisory","advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2019-20043"},{"url":"https://github.com/advisories/GHSA-ppxh-5qq2-77g8"},{"url":"https://security-tracker.debian.org/tracker/CVE-2019-20043","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2019-20043","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2019-20043","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2019-20043","description":"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.","status":"published","published":"2019-12-27T07:14:16Z","modified":"2024-08-05T02:32:10.528Z","updated_at":"2026-11-02T14:20:17.431882Z"}],"euvd":[{"id":"EUVD-2019-10599","description":"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.","status":"published","published":"2019-12-27T07:14:16Z","modified":"2024-08-05T02:32:10Z","updated_at":"2026-11-03T02:40:23.251012Z"}],"ghsa":[{"id":"GHSA-ppxh-5qq2-77g8","title":"WordPress before 5.3.1 allowed an unauthenticated user to make a post sticky through the REST API...","description":"WordPress before 5.3.1 allowed an unauthenticated user to make a post sticky through the REST API because of missing access control in wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php.","status":"published","published":"2022-05-24T17:05:11Z","modified":"2023-01-28T05:06:21Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","level":"medium"}],"cwes":["CWE-269"],"updated_at":"2026-11-02T14:44:25.86191Z"}],"nvd":[{"id":"CVE-2019-20043","description":"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.","status":"published","published":"2019-12-27T08:15:09.807Z","modified":"2026-06-17T02:29:53.117Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","level":"medium","assessor":"primary"},{"version":"2.0","score":5,"vector":"AV:N/AC:L/Au:N/C:N/I:P/A:N","level":"medium","assessor":"primary"}],"cwes":["CWE-269"],"updated_at":"2026-11-02T14:05:41.313583Z"}],"osv":[{"id":"CVE-2019-20043","description":"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.","status":"published","published":"2019-12-27T08:15:09.807Z","modified":"2026-10-24T10:49:51.530266018Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T15:44:12.010761Z"},{"id":"DEBIAN-CVE-2019-20043","description":"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.","status":"published","published":"2019-12-27T08:15:09.807Z","modified":"2026-09-21T07:01:38.885502048Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T15:45:32.221385Z"},{"id":"UBUNTU-CVE-2019-20043","description":"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.","status":"published","published":"2019-12-27T08:15:00Z","modified":"2025-10-24T04:48:07Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T15:54:21.213407Z"},{"id":"DSA-4599-1","title":"wordpress - security update","status":"published","published":"2020-01-08T00:00:00Z","modified":"2026-03-09T02:10:46.782323Z","updated_at":"2026-11-02T15:46:17.19998Z"}]}}