In WordPress before 4.7.5, there is improper handling of post meta data values in the XML-RPC API.

published 2017-05-18 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-18001

cvss: 8.6; version 3.0, 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

Patch / fix

distros 1 links 4

wordpress Debian 14, Debian 13, Debian 12 4.7.5+dfsg-1

debian advisories DEBIAN-CVE-2017-9062

github.com/WordPress/WordPress@3d95e3a commit
wordpress.org/news/2017/05/wordpress-4-7-5/ advisory
wpvulndb.com/vulnerabilities/8816 advisory
codex.wordpress.org/Version_4.7.5 advisory

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.0	8.6	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:P/A:N

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation
CWE-352 Cross-Site Request Forgery
CWE-601 URL Redirection to Untrusted Site

Technology feeds

WordPress rss critical rss

References

github.com /WordPress/WordPress/commit/3d95e3ae816f4d7c638f40d3e936a4be19724381
patch, third-party-advisory
wordpress.org /news/2017/05/wordpress-4-7-5/
patch, vendor-advisory
wpvulndb.com /vulnerabilities/8816
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-9062
NVD CVE-2017-9062

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.

Summary