CVE-2007-6013 in the critical feed json
Wordpress 1.5 through 2.3.1 uses cookie values based on the MD5 hash of a password MD5 hash, which allows attackers to bypass authenticatio…
published 2007-11-19 18 y ago modified 2026-06-16 4 mo ago also EUVD-2007-5983
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.3%
- EPSS 3.3% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
Wordpress 1.5 through 2.3.1 uses cookie values based on the MD5 hash of a password MD5 hash, which allows attackers to bypass authentication by obtaining the MD5 hash from the user database, then generating the authentication cookie from that hash.
Patch / fix
- wordpress Debian 14, Debian 13, Debian 12 2.5.0-1
debian advisories DEBIAN-CVE-2007-6013
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2007-6013 updated
wordpress cookie authentication vulnerability
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
3.28% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- trac.wordpress.org http://trac.wordpress.org/ticket/5367 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-327 Use of a Broken or Risky Cryptographic Algorithm
- Technology feeds
References
-
trac.wordpress.org
/ticket/5367
exploit, issue-tracking
-
redhat.com
/archives/fedora-package-announce/2008-January/msg00098.html
vendor-advisory, mailing-list
-
redhat.com
/archives/fedora-package-announce/2008-January/msg00079.html
vendor-advisory, mailing-list
-
vupen.com
/english/advisories/2007/3941
vdb-entry, broken-link, vendor-advisory
-
secunia.com
/advisories/28310
third-party-advisory, broken-link, vendor-advisory
-
secunia.com
/advisories/27714
third-party-advisory, broken-link, vendor-advisory
-
lists.grok.org.uk
/pipermail/full-disclosure/2007-November/058576.html
mailing-list, broken-link
-
cl.cam.ac.uk
/~sjm217/advisories/wordpress-cookie-auth.txt
third-party-advisory
-
securityreason.com
/securityalert/3375
third-party-advisory, broken-link
-
securityfocus.com
/archive/1/483927/100/0/threaded
mailing-list, broken-link, third-party-advisory, vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/38578
vdb-entry, third-party-advisory
-
securitytracker.com
/id?1018980
vdb-entry, broken-link, third-party-advisory
-
osvdb.org
/40801
vdb-entry, broken-link
Sources
- CVE List CVE-2007-6013
- NVD CVE-2007-6013
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.