CVE-2019-20043 · cross-distro fix matrix

CVE-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 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 all

Affects 3 Linux releases across 3 (distro × package) combinations.

Fix per ecosystem

Each block below is a distro release where CVE-2019-20043 has a known fix. Run the listed command on that distro to remediate.

Debian bullseye

Source: Debian Security Tracker

wordpress→ fixed in5.3.2+dfsg1-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y wordpress
```

Debian bookworm

Source: Debian Security Tracker

wordpress→ fixed in5.3.2+dfsg1-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y wordpress
```

Debian trixie

Source: Debian Security Tracker

wordpress→ fixed in5.3.2+dfsg1-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y wordpress
```

Are YOU affected by CVE-2019-20043?

5-second check on your actual server. Reads /etc/os-release, uname -r, and the distro's package manager; matches against this same cross-source index live.

curl https://mindsparkstack.com/scan.sh | bash

Form-based quickscan View on NVD

Continuous monitoring beats manual checking

CVE-2019-20043dropped silently in your distro's update channel. Every new CVE is the same story. StackPatch runs the matcher hourly against all 5 sources and emails the exact remediation when something new applies to one of your servers. $99 lifetime, 50 founder seats, 30-day refund.

See StackPatch ($99 lifetime)