A vulnerability classified as critical has been found in WordPress up to 5.3.1 (Content Management System). This affects some unknown functionality of the file wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php of the component REST API. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was disclosed 12/27/2019. This vulnerability is uniquely identified as CVE-2019-20043 since 12/27/2019. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 12/27/2019). The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

By approaching the search of inurl:wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The entries 147806 and 147805 are pretty similar.

Productinfo

Type

• Content Management System

Name

• WordPress

Version

• 5.3.0
• 5.3.1

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion