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)
EPSS: 0.035 (88.0th percentile) — read the EPSS interpretation.
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.
Affected products
- Wordpress
- Debian Debian_linux — versions 8.0
- N/a — versions n/a
Weakness classification (CWE)
Public proof-of-concept exploits
References
- cve@mitre.org (VDB Entry, Third Party Advisory, vdb-entry, x_refsource_SECTRACK, Broken Link)
- cve@mitre.org (x_refsource_MISC, Broken Link)
- cve@mitre.org (x_refsource_CONFIRM, Release Notes)
- cve@mitre.org (vendor-advisory, Mailing List, x_refsource_DEBIAN)
- cve@mitre.org (Patch, x_refsource_MISC)
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.