Skip to content
Fencer Vulns
medium 5.3

CVE-2021-39200 json

Information Disclosure in wp_die() via JSONP in wordpress

published 2021-09-09 5 y ago modified 2026-09-08 2 mo ago also BIT-wordpress-2021-39200 , BIT-wordpress-multisite-2021-39200 , EUVD-2021-25582 , GHSA-m9hc-7v5q-x8q5

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.0%
EPSS 2.0% chance of exploitation in 30 days, percentile 80%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami wordpress 5.8.1
  • bitnami wordpress-multisite 5.8.1
  • wordpress wordpress 5.8.1
  • wordpress Debian 14, Debian 13, Debian 12 5.8.1+dfsg1-1

debian advisories DEBIAN-CVE-2021-39200

  • wordpress Arch Linux 5.8.1-1

arch linux advisories AVG-2373

Exploit prediction

1.97% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N
OSV 3.1 5.3 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
bitnami wordpress
>=5.2.0, <5.8.1
5.8.1
bitnami wordpress-multisite
>=5.2.0, <5.8.1
5.8.1

Affected products

  • WordPress wordpress-develop

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of WordPress/wordpress-develop published their own advisory on GitHub. Reviewed sources take precedence over it.