Strategic Overview
- Status
- Patched in 3.7.2
- Affected Core
- WordPress 3.8
- Affected Version
3.7 – 3.8.1 · 3 branches- CVSS
- 6.5Medium
- Weakness type
- CWE-287 · Improper Authentication
- CVE
CVE-2014-0166
At a glance
CVE-2014-0166 is a medium-severity Improper Authentication vulnerability in the WordPress 3.8 WordPress release line, affecting 3.7 – 3.8.1 · 3 branches. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.7.2; sites on affected versions should update now. Disclosed April 2014, reported by Jon Cave.
Vulnerability Overview
The wp_validate_auth_cookie function in wp-includes/pluggable.php in WordPress before 3.7.2 and 3.8.x before 3.8.2 does not properly determine the validity of authentication cookies, which makes it easier for remote attackers to obtain access via a forged cookie.
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 privileges on the target site, and no interaction from a victim user.
CWE-287: Improper Authentication
Reaching this weakness in WordPress 3.8 3.7 – 3.8.1 · 3 branches takes a caller who can reach the endpoint. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.
An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For WordPress 3.8 the fix is 3.7.2: builds 3.7 – 3.8.1 · 3 branches are affected, anything from 3.7.2 onward is not.
Remediation
Update to one of the following versions, or a newer patched version: 3.7.2, 3.8.2
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: updating to 3.7.2 is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WordPress 3.8
- 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