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.

INFO

Published Date :

Dec. 27, 2019, 8:15 a.m.

Last Modified :

Jan. 20, 2023, 4:11 p.m.

Remotely Exploitable :

Yes !

Impact Score :

1.4

Exploitability Score :

2.8
Public PoC/Exploit Available at Github

CVE-2019-20043 has a 3 public PoC/Exploit available at Github. Go to the Public Exploits tab to see the list.

Affected Products

The following products are affected by CVE-2019-20043 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Debian debian_linux
1 Wordpress wordpress
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2019-20043.

URL Resource
https://core.trac.wordpress.org/changeset/46893/trunk Patch
https://github.com/WordPress/wordpress-develop/commit/1d1d5be7aa94608c04516cac4238e8c22b93c1d9 Third Party Advisory
https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-g7rg-hchx-c2gw Third Party Advisory
https://seclists.org/bugtraq/2020/Jan/8 Mailing List Third Party Advisory
https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/ Release Notes Vendor Advisory
https://wpvulndb.com/vulnerabilities/9973 Release Notes Third Party Advisory
https://www.debian.org/security/2020/dsa-4599 Third Party Advisory
https://www.debian.org/security/2020/dsa-4677 Third Party Advisory

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

WordPress Pen Testing

Updated: 3 months, 2 weeks ago
3 stars 0 fork 0 watcher
Born at : Oct. 23, 2022, 8:42 p.m. This repo has been linked 100 different CVEs too.

Desarrollo del CTF DerpNStink

Updated: 3 years, 6 months ago
0 stars 1 fork 1 watcher
Born at : April 22, 2021, 1:40 p.m. This repo has been linked 41 different CVEs too.

Desarrollo del CTF SYMFONOS

Updated: 3 years, 7 months ago
0 stars 0 fork 0 watcher
Born at : March 28, 2021, 1:13 a.m. This repo has been linked 46 different CVEs too.

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2019-20043 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2019-20043 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Modified by [email protected]

    May. 14, 2024

    Action Type Old Value New Value
  • Modified Analysis by [email protected]

    Jan. 20, 2023

    Action Type Old Value New Value
    Removed CVSS V3.1 NIST AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
    Added CVSS V3.1 NIST AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
    Changed Reference Type https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-g7rg-hchx-c2gw No Types Assigned https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-g7rg-hchx-c2gw Third Party Advisory
    Changed Reference Type https://seclists.org/bugtraq/2020/Jan/8 No Types Assigned https://seclists.org/bugtraq/2020/Jan/8 Mailing List, Third Party Advisory
    Changed Reference Type https://www.debian.org/security/2020/dsa-4599 No Types Assigned https://www.debian.org/security/2020/dsa-4599 Third Party Advisory
    Changed Reference Type https://www.debian.org/security/2020/dsa-4677 No Types Assigned https://www.debian.org/security/2020/dsa-4677 Third Party Advisory
    Changed CPE Configuration OR *cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:* versions up to (excluding) 5.3.1 OR *cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:* versions from (including) 3.7 up to (excluding) 5.3.1
    Added CPE Configuration OR *cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:* *cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
  • CVE Modified by [email protected]

    May. 06, 2020

    Action Type Old Value New Value
    Added Reference https://www.debian.org/security/2020/dsa-4677 [No Types Assigned]
  • CVE Modified by [email protected]

    Jan. 10, 2020

    Action Type Old Value New Value
    Changed 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. 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.
    Added Reference https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-g7rg-hchx-c2gw [No Types Assigned]
  • CVE Modified by [email protected]

    Jan. 08, 2020

    Action Type Old Value New Value
    Added Reference https://www.debian.org/security/2020/dsa-4599 [No Types Assigned]
    Added Reference https://seclists.org/bugtraq/2020/Jan/8 [No Types Assigned]
  • Initial Analysis by [email protected]

    Dec. 31, 2019

    Action Type Old Value New Value
    Added CVSS V2 NIST (AV:N/AC:L/Au:N/C:N/I:P/A:N)
    Added CVSS V3.1 NIST AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
    Changed Reference Type https://core.trac.wordpress.org/changeset/46893/trunk No Types Assigned https://core.trac.wordpress.org/changeset/46893/trunk Patch
    Changed Reference Type https://github.com/WordPress/wordpress-develop/commit/1d1d5be7aa94608c04516cac4238e8c22b93c1d9 No Types Assigned https://github.com/WordPress/wordpress-develop/commit/1d1d5be7aa94608c04516cac4238e8c22b93c1d9 Third Party Advisory
    Changed Reference Type https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/ No Types Assigned https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/ Release Notes, Vendor Advisory
    Changed Reference Type https://wpvulndb.com/vulnerabilities/9973 No Types Assigned https://wpvulndb.com/vulnerabilities/9973 Release Notes, Third Party Advisory
    Added CWE NIST CWE-269
    Added CPE Configuration OR *cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:* versions up to (excluding) 5.3.1
  • CVE Modified by [email protected]

    Dec. 27, 2019

    Action Type Old Value New Value
    Added Reference https://wpvulndb.com/vulnerabilities/9973 [No Types Assigned]
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2019-20043 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2019-20043 weaknesses.

Exploit Prediction

EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.

0.28 }} 0.08%

score

0.67972

percentile

CVSS31 - Vulnerability Scoring System
Attack Vector
Attack Complexity
Privileges Required
User Interaction
Scope
Confidentiality
Integrity
Availability