Strategic Overview
- Status
- Patched in 4.4
- Affected Core
- WordPress 4.4
- Affected Version
< 4.4- CVSS
- 7.5High
- Weakness type
- CWE-261 · Weak Encoding for Password
- CVE
CVE-2014-6412
At a glance
CVE-2014-6412 is a high-severity Weak Encoding for Password vulnerability in the WordPress 4.4 WordPress release line, affecting < 4.4. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 4.4; sites on affected versions should update now. Disclosed February 2015.
Vulnerability Overview
WordPress before 4.4 makes it easier for remote attackers to predict password-recovery tokens via a brute-force approach.
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. A successful exploit has high impact on confidentiality.
CWE-261: Weak Encoding for Password
Obscuring a password with a trivial encoding does not protect the password.
Remediation
Update to version 4.4, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: updating to 4.4 is the step that ends it.
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WordPress 4.4
- 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