CVE-2017-9063 json
In WordPress before 4.7.5, a cross-site scripting (XSS) vulnerability related to the Customizer exists, involving an invalid customization…
published 2017-05-18 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-18002
- cvss
- 6.1
- 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 80%
- public exploits
- 0
- none known
Summary
In WordPress before 4.7.5, a cross-site scripting (XSS) vulnerability related to the Customizer exists, involving an invalid customization session.
Patch / fix
- wordpress Debian 14, Debian 13, Debian 12 4.7.5+dfsg-1
debian advisories DEBIAN-CVE-2017-9063
- github.com/WordPress/WordPress@3d10fef commit
- wordpress.org/news/2017/05/wordpress-4-7-5/ advisory
- wpvulndb.com/vulnerabilities/8820 advisory
- codex.wordpress.org/Version_4.7.5 advisory
Exploit prediction
2.00% chance of exploitation in the next 30 days, higher than 80% 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/3d10fef22d788f29aed745b0f5ff6f6baea69af3
patch, third-party-advisory
-
wordpress.org
/news/2017/05/wordpress-4-7-5/
patch, vendor-advisory
-
wpvulndb.com
/vulnerabilities/8820
patch, third-party-advisory
-
codex.wordpress.org
/Version_4.7.5
patch, release-notes, vendor-advisory
-
debian.org
/security/2017/dsa-3870
vendor-advisory, third-party-advisory
-
securitytracker.com
/id/1038520
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/98509
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-9063
- NVD CVE-2017-9063
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.