SSRF in WordPress
CVE-2016-4029
WordPress before 4.5 does not consider octal and hexadecimal IP address formats when determining an intranet address, which allows remote attackers to bypass an intended SSRF protection mechanism via a crafted address.
Vulnerability class: SSRF (Server-Side Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 8.6 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N.
EPSS exploit prediction
EPSS: 0.035 (88.8th percentile), scored .
Low probability of exploitation in the next 30 days, but still tracked. 89th percentile — 88.8% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.035 · newest: 0.035 · change: 0.000
Affected products
- WordPress
- Debian Linux — versions 8.0
Weakness classification (CWE)
Public proof-of-concept exploits
References
- www.securitytracker.com/id/1036594 (VDB Entry, Third Party Advisory, vdb-entry, Broken Link)
- wpvulndb.com/vulnerabilities/8473 (Broken Link)
- codex.wordpress.org/Version_4.5 (Release Notes)
- www.debian.org/security/2016/dsa-3681 (vendor-advisory, Mailing List)
- core.trac.wordpress.org/query (Patch)
Frequently asked questions
- What is CVE-2016-4029?
- CVE-2016-4029 is a high-severity vulnerability in WordPress, classified under Server-Side Request Forgery (SSRF). CVSS score: 8.6/10. Published 2016-08-07.
- How severe is CVE-2016-4029?
- High severity. CVSS v3 base score is 8.6 out of 10.
- Is CVE-2016-4029 known to be exploited?
- 6 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.