CVE-2019-20043Not scoredCWE-269

CVE-2019-20043: Wordpress vulnerability

Wordpress

Vendor fix available · Affected: Wordpress · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

2.5%probability of exploitation in the next 30 days

84th percentile

050100

Higher than 84% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

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.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Improper Privilege Management · Access Control
Vendor: Wordpress
Published: December 2019
Band: Possible (1 to 10%), December 2019

CoverageNo articles yet

No CyberSIXT article names CVE-2019-20043 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.