Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2021-39200

WordPress is a free and open-source content management system written ...

Overview

Published
9 Sep 2021
Modified
17 Jun 2026
Medium CVE
2 Registry packages
1 OS packages
2 Linux distributions
Yes Fix available

Description

WordPress is a free and open-source content management system written in PHP and paired with a MySQL or MariaDB database. In affected versions output data of the function wp_die() can be leaked under certain conditions, which can include data like nonces. It can then be used to perform actions on your behalf. This has been patched in WordPress 5.8.1, along with any older affected versions via minor releases. It's strongly recommended that you keep auto-updates enabled to receive the fix.

Source: OX vulnerability database

Severity

5.3 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

Weakness: CWE-200

Affected packages · 2

Packages affected by CVE-2021-39200
EcosystemPackageVulnerableFixed in
Bitnami wordpress >=5.2.0, <5.8.1 5.8.1
Bitnami wordpress-multisite >=5.2.0, <5.8.1 5.8.1

Open a package to see all its vulnerabilities.

Operating systems · 5 fixes

debian 4 releases · 1 package

fixed 4
wordpress
debian fixes for CVE-2021-39200
ReleasePackageFixed in
11 wordpress 5.7.3+dfsg1-0+deb11u1
12 wordpress 5.8.1+dfsg1-1
13 wordpress 5.8.1+dfsg1-1
14 wordpress 5.8.1+dfsg1-1

echo 1 release · 1 package

fixed 1
wordpress
echo fixes for CVE-2021-39200
ReleasePackageFixed in
wordpress 5.8.1+dfsg1-1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.