Skip to content
Fencer Intel
medium 5.4

CVE-2019-16223 json

WordPress before 5.2.3 allows XSS in post previews by authenticated users.

published 7y ago modified 4mo ago also EUVD-2019-7035

cvss
5.4
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
5.2%
EPSS 5.2% chance of exploitation in 30 days, percentile 92%
public exploits
1
Exploit-DB

Summary

WordPress before 5.2.3 allows XSS in post previews by authenticated users.

Patch / fix

  • wordpress wordpress 5.2.3
  • wordpress Debian 14, Debian 13, Debian 12 5.2.3+dfsg1-1

debian advisories DEBIAN-CVE-2019-16223

Is CVE-2019-16223 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-16223 updated cvss 5.4

wordpress: XSS in post previews by authenticated users

  • Red Hat All currently supported Red Hat products
    not 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

Timeline

  1. Published
  2. First public exploit (EDB-49338)

Exploit prediction

5.18% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-49338 Wordpress Core 5.2.2 - 'post previews' XSS webapps, 2021-01-04
  • packetstormsecurity.com http://packetstormsecurity.com/files/160745/WordPress-Core-5.2.2-Cross-Site-Scripting.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 3.5 AV:N/AC:M/Au:S/C:N/I:P/A:N

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation
Technology feeds

References

Sources

Fencer Intel 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.