WordPress before 4.5 does not consider octal and hexadecimal IP address formats when…
Priority MEDIUM 44CWE-918Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- None · High · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA.
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.
Why it matters now
EPSS 0.03965 90th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | — | all versions | — | No fix listed | CNA |
- — Vendor— Affected all versions Fixed in — No fix listed CNA
Remediation
No fixed version listed by the sources yet.
Vendor assessments
Timeline
- 2026-10-02 Threatist record created from CVE-2016-4029
- 2026-10-03 Alias added: GHSA-j2rp-vprg-5m9q
- 2026-10-04 EPSS moved to the 90th–95th percentile
References
Sources
- CVE-2016-4029 · CVE Program
- CVE-2016-4029 · NVD
- FIRST EPSS
- GHSA-j2rp-vprg-5m9q · GitHub Advisory Database · CC BY 4.0
- CVE-2016-4029 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences