Server-Side Request Forgery (SSRF) Affecting wordpress package, versions <4.7.5+dfsg-1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-ECHOLATEST-WORDPRESS-18067569
- published21 Jul 2026
- disclosed18 May 2017
Introduced: 18 May 2017
CVE-2017-9066 (opens in a new tab)How to fix?
Upgrade Echo:latest wordpress to version 4.7.5+dfsg-1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream wordpress package and not the wordpress package as distributed by Echo.
See How to fix? for Echo:latest relevant fixed versions and status.
In WordPress before 4.7.5, there is insufficient redirect validation in the HTTP class, leading to SSRF.
References
- https://advisory.echohq.com/cve/CVE-2017-9066
- https://www.cve.org/CVERecord?id=CVE-2017-9066
- http://www.securityfocus.com/bid/98509
- http://www.securitytracker.com/id/1038520
- https://codex.wordpress.org/Version_4.7.5
- https://github.com/WordPress/WordPress/commit/76d77e927bb4d0f87c7262a50e28d84e01fd2b11
- https://twitter.com/skansing/status/865362551097393153
- https://wordpress.org/news/2017/05/wordpress-4-7-5/
- https://wpvulndb.com/vulnerabilities/8815
- https://www.debian.org/security/2018/dsa-4090