CVE-2019-20043
published 2019-12-27CVE-2019-20043: 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…
PriorityP424medium4.3CVSS 3.1
AVNACLPRLUINSUCNILAN
EPSS
2.42%
82.3th percentile
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
8 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | debian_linux | — | — |
| debian | wordpress | < wordpress 5.3.2+dfsg1-1 (bookworm) | wordpress 5.3.2+dfsg1-1 (bookworm) |
| wordpress | wordpress | >= 0 < 5.3.2+dfsg1-1 | 5.3.2+dfsg1-1 |
| wordpress | wordpress | >= 0 < 5.3.2+dfsg1-1 | 5.3.2+dfsg1-1 |
| wordpress | wordpress | >= 0 < 5.3.2+dfsg1-1 | 5.3.2+dfsg1-1 |
| wordpress | wordpress | >= 0 < 5.3.2+dfsg1-1 | 5.3.2+dfsg1-1 |
| wordpress | wordpress | >= 3.7 < 5.3.1 | 5.3.1 |
CVSS provenance
nvdv3.14.3MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:P/A:N
osv4.3MEDIUM
vendor_debian4.3MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-ppxh-5qq2-77g8: WordPress before 5
ghsa_unreviewed·2022-05-24
CVE-2019-20043 [MEDIUM] CWE-269 GHSA-ppxh-5qq2-77g8: WordPress before 5
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.
OSV
CVE-2019-20043: In in wp-includes/rest-api/endpoints/class-wp-rest-posts-controller
osv·2019-12-27·CVSS 4.3
CVE-2019-20043 [MEDIUM] CVE-2019-20043: In in wp-includes/rest-api/endpoints/class-wp-rest-posts-controller
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.
Debian
CVE-2019-20043: wordpress - In in wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php in WordP...
vendor_debian·2019·CVSS 4.3
CVE-2019-20043 [MEDIUM] CVE-2019-20043: wordpress - In in wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php in WordP...
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.
Scope: local
bookworm: resolved (fixed in 5.3.2+dfsg1-1)
bullseye: resolved (fixed in 5.3.2+dfsg1-1)
forky: resolved (fixed in 5.3.2+dfsg1-1)
sid: resolved (fixed in 5.3.2+dfsg1-1)
trixie: resolved (fixed in 5.3.2+dfsg1-1)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2019-20043 wordpress: 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
bugzilla·2020-01-21·CVSS 4.3
CVE-2019-20043 [MEDIUM] CVE-2019-20043 wordpress: 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
CVE-2019-20043 wordpress: 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
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.
Reference:
https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-g7rg-hchx-c2gw
Upstream commit:
https://github.com/WordPress/wordpress-develop/commit/1d1d5be7aa94608c04516ca
Bugzilla
CVE-2019-20043 wordpress: 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 [epel-7]
bugzilla·2020-01-21·CVSS 4.3
CVE-2019-20043 [MEDIUM] CVE-2019-20043 wordpress: 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 [epel-7]
CVE-2019-20043 wordpress: 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 [epel-7]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-7.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and
Bugzilla
CVE-2019-20043 wordpress: 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 [epel-6]
bugzilla·2020-01-21·CVSS 4.3
CVE-2019-20043 [MEDIUM] CVE-2019-20043 wordpress: 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 [epel-6]
CVE-2019-20043 wordpress: 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 [epel-6]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-6.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and
https://core.trac.wordpress.org/changeset/46893/trunkhttps://github.com/WordPress/wordpress-develop/commit/1d1d5be7aa94608c04516cac4238e8c22b93c1d9https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-g7rg-hchx-c2gwhttps://seclists.org/bugtraq/2020/Jan/8https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/https://wpvulndb.com/vulnerabilities/9973https://www.debian.org/security/2020/dsa-4599https://www.debian.org/security/2020/dsa-4677https://core.trac.wordpress.org/changeset/46893/trunkhttps://github.com/WordPress/wordpress-develop/commit/1d1d5be7aa94608c04516cac4238e8c22b93c1d9https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-g7rg-hchx-c2gwhttps://seclists.org/bugtraq/2020/Jan/8https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/https://wpvulndb.com/vulnerabilities/9973https://www.debian.org/security/2020/dsa-4599https://www.debian.org/security/2020/dsa-4677
2019-12-27
Published