LiveActive security incident?Get immediate response
CVE Record

CVE-2019-20043: In in wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php in WordPress 3.7 to 5.3.0, authenti...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This WordPress flaw let a logged-in user with limited publishing rights change whether posts were marked sticky. That could affect what content appears prominently, but the sources do not show site takeover, unauthenticated access, or active exploitation.

Executive priority

Treat as a routine but real content-integrity issue. Prioritize remediation on public sites with many contributor accounts or editorial workflows, especially if they run old WordPress versions.

Technical view

CVE-2019-20043 affects WordPress 3.7 through 5.3.0 in the REST posts controller. Authenticated users without publish permission, such as contributors, could set or unset the sticky status through the REST API. WordPress patched it in 5.3.1 and backported fixes to older maintained branches.

Likely exposure

Exposure is most likely on WordPress sites running 3.7 to 5.3.0, including distro-packaged WordPress before the referenced Debian security updates. Risk requires an authenticated account with insufficient post-publishing rights.

Exploitation context

The provided sources do not report known active exploitation, and the CVE is not listed as KEV. The practical abuse is privilege bypass affecting content state, not proven remote code execution or unauthenticated compromise.

Researcher notes

Key evidence names the REST posts controller and unauthorized sticky or unsticky changes. Public sources identify the fix in WordPress 5.3.1, a core changeset, a GitHub commit, and Debian security advisories. No CVSS, CWE, or exploit evidence was provided.

Mitigation direction

  • Upgrade WordPress to 5.3.1 or a later supported release.
  • Apply the corresponding vendor or distribution security update.
  • Verify older WordPress branches received the backported minor release fix.
  • Review low-privilege WordPress accounts and remove unnecessary access.
  • Check vendor guidance if using managed or packaged WordPress builds.

Validation and detection

  • Inventory WordPress versions and flag 3.7 through 5.3.0.
  • Confirm the installed build includes the 5.3.1 security fix or backport.
  • Review contributor and low-privilege account activity for unexpected sticky changes.
  • Check package changelogs against Debian DSA-4599 or DSA-4677 where applicable.
Prepared
Confidence
high
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-20043 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
9Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.