CVE-2016-4029 json
WordPress before 4.5 does not consider octal and hexadecimal IP address formats when determining an intranet address, which allows remote a…
published 2016-08-07 10 y ago modified 2026-06-17 4 mo ago also EUVD-2016-5035
- cvss
- 8.6
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.0%
- EPSS 4.0% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- wordpress wordpress 4.5
- wordpress Debian 14, Debian 13, Debian 12 4.5+dfsg-1
debian advisories DEBIAN-CVE-2016-4029
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2016-4029 updated
wordpress: 4.5 release security fixes
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
3.96% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.6 | CVSS:3.1/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-918 Server-Side Request Forgery
- Technology feeds
References
-
core.trac.wordpress.org
/query?status=closed&milestone=4.5
patch
-
debian.org
/security/2016/dsa-3681
vendor-advisory, mailing-list
-
securitytracker.com
/id/1036594
vdb-entry, broken-link, third-party-advisory
-
wpvulndb.com
/vulnerabilities/8473
broken-link
-
codex.wordpress.org
/Version_4.5
release-notes
Sources
- CVE List CVE-2016-4029
- NVD CVE-2016-4029
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.