| Name | CVE-2012-6707 |
| Description | 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. |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
| Debian Bugs | 880868 |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|
| wordpress (PTS) | bullseye (security), bullseye | 5.7.11+dfsg1-0+deb11u1 | vulnerable |
| bookworm, bookworm (security) | 6.1.6+dfsg1-0+deb12u1 | vulnerable |
| sid, trixie | 6.6.1+dfsg1-1 | vulnerable |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|
| wordpress | source | (unstable) | (unfixed) | | | 880868 |
Notes
[bookworm] - wordpress <postponed> (Minor issue, can be revisited with upstream has picked a new hashing solution)
[bullseye] - wordpress <postponed> (Minor issue, can be revisited with upstream has picked a new hashing solution)
[buster] - wordpress <postponed> (Minor issue, can be revisited with upstream has picked a new hashing solution)
[stretch] - wordpress <postponed> (Minor issue, can be revisited with upstream has picked a new hashing solution)
[jessie] - wordpress <postponed> (Minor issue, can be revisited with upstream has picked a new hashing solution)
[wheezy] - wordpress <postponed> (Minor issue, can be revisited with upstream has picked a new hashing solution)
https://core.trac.wordpress.org/ticket/21022
Proposed patch (but not merged): https://core.trac.wordpress.org/attachment/ticket/21022/21022.3.diff
Cf. https://core.trac.wordpress.org/ticket/21022#comment:80 and following.