CVE-2019-16221 json
WordPress before 5.2.3 allows reflected XSS in the dashboard.
published 2019-09-11 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-7033
- cvss
- 6.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
WordPress before 5.2.3 allows reflected XSS in the dashboard.
Patch / fix
- wordpress wordpress 5.2.3
- wordpress Debian 14, Debian 13, Debian 12 5.2.3+dfsg1-1
debian advisories DEBIAN-CVE-2019-16221
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2019-16221 updated cvss 6.1
wordpress: reflected XSS in the dashboard
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.77% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
-
debian.org
/security/2020/dsa-4599
vendor-advisory, third-party-advisory
-
debian.org
/security/2020/dsa-4677
vendor-advisory, third-party-advisory
-
wordpress.org
/news/2019/09/wordpress-5-2-3-security-and-maintenance-release/
release-notes, vendor-advisory
-
wpvulndb.com
/vulnerabilities/9865
third-party-advisory
-
lists.debian.org
/debian-lts-announce/2019/10/msg00023.html
mailing-list, third-party-advisory
-
seclists.org
/bugtraq/2020/Jan/8
mailing-list, third-party-advisory
Sources
- CVE List CVE-2019-16221
- NVD CVE-2019-16221
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.