CVE-2012-6707
Reported by mitre · Published October 19, 2017
WordPress through 4.8.2 uses a weak MD5-based password hashing algorithm, which makes it easier for attackers to determine cleartext values by leveraging access to the hash values. NOTE: the approach to changing this may not be fully compatible with certain use cases, such as migration of a WordPress site from a web host that uses a recent PHP version to a different web host that uses PHP 5.2. These use cases are plausible (but very unlikely) based on statistics showing widespread deployment of WordPress with obsolete PHP versions.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| wordpress | wordpress | 4.8.2 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| n/a | n/a | n/a |
| n/a | n/a | * |
Timeline
- Oct 19, 2017 CVE Published
- Feb 4, 2022 EPSS Score (30 in total, the first dated here)
- Sep 17, 2024 CVE Updated
- Apr 6, 2026 Security Advisory
- Oct 25, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2012-6707
vulnetix vdb fixes CVE-2012-6707
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2012-6707/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart