CVE-2018-20153 json
In WordPress before 4.9.9 and 5.x before 5.0.1, contributors could modify new comments made by users with greater privileges, possibly caus…
published 2018-12-14 7 y ago modified 2026-06-17 4 mo ago also EUVD-2018-12722
- cvss
- 5.4
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
In WordPress before 4.9.9 and 5.x before 5.0.1, contributors could modify new comments made by users with greater privileges, possibly causing XSS.
Patch / fix
- wordpress wordpress 4.9.9, 5.0.1
- wordpress Debian 14, Debian 13, Debian 12 5.0.1+dfsg1-1
debian advisories DEBIAN-CVE-2018-20153
Exploit prediction
2.05% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.4 | CVSS:3.0/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
-
debian.org
/security/2019/dsa-4401
vendor-advisory, third-party-advisory
-
wordpress.org
/support/wordpress-version/version-5-0-1/
release-notes, vendor-advisory
-
codex.wordpress.org
/Version_4.9.9
product, release-notes, vendor-advisory
-
wpvulndb.com
/vulnerabilities/9172
vendor-advisory
-
wordpress.org
/news/2018/12/wordpress-5-0-1-security-release/
release-notes, vendor-advisory
-
securityfocus.com
/bid/106220
vdb-entry, third-party-advisory
-
lists.debian.org
/debian-lts-announce/2019/02/msg00019.html
mailing-list, third-party-advisory
-
zdnet.com
/article/wordpress-plugs-bug-that-led-to-google-indexing-some-user-passwords/
press/media-coverage, third-party-advisory
Sources
- CVE List CVE-2018-20153
- NVD CVE-2018-20153
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.