CVE-2018-10102 json
Before WordPress 4.9.5, the version string was not escaped in the get_the_generator function, and could lead to XSS in a generator tag.
published 2018-04-14 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-2181
- cvss
- 6.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.3%
- EPSS 4.3% chance of exploitation in 30 days, percentile 91%
- public exploits
- 0
- none known
Summary
Before WordPress 4.9.5, the version string was not escaped in the get_the_generator function, and could lead to XSS in a generator tag.
Patch / fix
- wordpress wordpress 4.9.5
- wordpress Debian 14, Debian 13, Debian 12 4.9.5+dfsg1-1
debian advisories DEBIAN-CVE-2018-10102
Exploit prediction
4.25% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.1 | CVSS:3.0/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
-
github.com
/WordPress/WordPress/commit/31a4369366d6b8ce30045d4c838de2412c77850d
patch, third-party-advisory
-
core.trac.wordpress.org
/changeset/42893
patch, third-party-advisory
-
debian.org
/security/2018/dsa-4193
vendor-advisory, third-party-advisory
-
codex.wordpress.org
/Version_4.9.5
vendor-advisory
-
securityfocus.com
/bid/103775
vdb-entry, third-party-advisory
-
wpvulndb.com
/vulnerabilities/9055
third-party-advisory, vdb-entry
-
securitytracker.com
/id/1040836
vdb-entry, third-party-advisory
-
wordpress.org
/news/2018/04/wordpress-4-9-5-security-and-maintenance-release/
third-party-advisory
-
lists.debian.org
/debian-lts-announce/2018/04/msg00031.html
mailing-list, third-party-advisory
Sources
- CVE List CVE-2018-10102
- NVD CVE-2018-10102
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.