Vulnerability in WordPress
CVE-2012-6707
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
EPSS exploit prediction
EPSS: 0.011 (64.5th percentile), scored .
Low probability of exploitation in the next 30 days, but still tracked. 65th percentile — 64.5% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.011 · newest: 0.011 · change: 0.000
Affected products
Weakness classification (CWE)
Public proof-of-concept exploits
References
- core.trac.wordpress.org/ticket/21022 (Patch, Issue Tracking, Vendor Advisory)
Frequently asked questions
- What is CVE-2012-6707?
- CVE-2012-6707 is a high-severity vulnerability in WordPress, classified under Inadequate Encryption Strength. CVSS score: 7.5/10. Published 2017-10-19.
- How severe is CVE-2012-6707?
- High severity. CVSS v3 base score is 7.5 out of 10.
- Is CVE-2012-6707 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.