WordPress Core < 4.9.5 - Security Misconfiguration with URL Hostnames
Strategic Overview
- Status
- Patched in 3.7.26
- Affected Core
- WordPress 4.9
- Affected Version
3.7 – 4.9.4 · 14 branches- CVSS
- 4.3Medium
- Weakness type
- CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
- CVE
CVE-2018-10101
At a glance
CVE-2018-10101 is a medium-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the WordPress 4.9 WordPress release line, affecting 3.7 – 4.9.4 · 14 branches. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 3.7.26; sites on affected versions should update now. Disclosed April 2018.
Vulnerability Overview
Before WordPress 4.9.5, the URL validator assumed URLs with the hostname localhost were on the same host as the WordPress server.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
Reaching this weakness in WordPress 4.9 3.7 – 4.9.4 · 14 branches takes a caller who can reach the endpoint. An open redirect is a page that takes a destination from the request and sends the browser there without checking that the destination belongs to the site.
A link that starts on a trusted domain finishes on an attacker's, which is what makes phishing and consent-screen abuse credible to the person clicking it. For WordPress 4.9 the fix is 3.7.26: builds 3.7 – 4.9.4 · 14 branches are affected, anything from 3.7.26 onward is not.
Remediation
Update to one of the following versions, or a newer patched version: 3.7.26, 3.8.26, 3.9.24, 4.0.23, 4.1.23, 4.2.20, 4.3.16, 4.4.15, 4.5.14, 4.6.11, 4.7.10, 4.8.6, 4.9.5
How does WordSec protect against this?
The attempt arrives as an ordinary request to WordPress 4.9: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: updating to 3.7.26 is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WordPress 4.9
- 9.8CVE-2026-63030: WordPress Core 6.9 - 7.0.1 Remote Code Execution
CVE-2026-63030 - 9.8CVE-2024-31211: WordPress Core 6.4.0 - 6.4.1 RCE POP Chain
CVE-2024-31211 - 9.8WordPress Core < 6.0.3 SQL Injection via WP_Date_Query
- 9.8CVE-2021-29476: WordPress Core < 5.5.3 PHP Object Injection Gadget
CVE-2021-29476 - 9.8CVE-2017-16510: WordPress Core SQL Injection
CVE-2017-16510 - 9.8CVE-2017-14723: WordPress Core < 4.8.2 SQL Injection
CVE-2017-14723 - 9.8CVE-2007-6013: WordPress Core 1.5 - 2.3.1 Authorization Bypass
CVE-2007-6013 - 9.8CVE-2007-6318: WordPress Core < 2.3.2 SQL Injection
CVE-2007-6318
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C