CVE-2020-11028 · cross-distro fix matrix

CVE-2020-11028: In affected versions of WordPress, some private posts, which were previously public, can result in unauthenticated disclosure under a specific set of conditions. This has been patched in version 5.4.1, along with all the previously affected versions via a minor release (5.3.3, 5.2.6, 5.1.5, 5.0.9, 4

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

Fix per ecosystem

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

Debian bullseye

Source: Debian Security Tracker

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

Debian bookworm

Source: Debian Security Tracker

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

Debian trixie

Source: Debian Security Tracker

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

Are YOU affected by CVE-2020-11028?

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-2020-11028dropped 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)