CVE-2017-9064 json
In WordPress before 4.7.5, a Cross Site Request Forgery (CSRF) vulnerability exists in the filesystem credentials dialog because a nonce is…
published 2017-05-18 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-18003
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
In WordPress before 4.7.5, a Cross Site Request Forgery (CSRF) vulnerability exists in the filesystem credentials dialog because a nonce is not required for updating credentials.
Patch / fix
- wordpress Debian 14, Debian 13, Debian 12 4.7.5+dfsg-1
debian advisories DEBIAN-CVE-2017-9064
- github.com/WordPress/WordPress@38347d7 commit
- wordpress.org/news/2017/05/wordpress-4-7-5/ advisory
- wpvulndb.com/vulnerabilities/8818 advisory
- codex.wordpress.org/Version_4.7.5 advisory
Exploit prediction
1.74% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
- Technology feeds
References
-
github.com
/WordPress/WordPress/commit/38347d7c580be4cdd8476e4bbc653d5c79ed9b67
patch, third-party-advisory
-
wordpress.org
/news/2017/05/wordpress-4-7-5/
patch, vendor-advisory
-
wpvulndb.com
/vulnerabilities/8818
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-9064
- NVD CVE-2017-9064
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.