CVE-2007-6013
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 3.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 3.3% in the next 30 days (EPSS).
- Severity: 9.8 CRITICAL (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 3.3% · EPSS, next 30 days
- Weakness
- CWE-327 · Broken cryptographic algorithm
- Record status
- Modified
Affected
- WordPress ≤ 2.3.1
- Fedoraproject Fedora 7
- Fedoraproject Fedora 8
Attack profile CVSS 3.1 · 9.8
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2007-6013.md and follow it. Check whether this project is affected by CVE-2007-6013. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- http://secunia.com/advisories/27714
- http://secunia.com/advisories/28310
- http://www.vupen.com/english/advisories/2007/3941
- http://secunia.com/advisories/27714
- http://secunia.com/advisories/28310
- http://www.vupen.com/english/advisories/2007/3941
References
- http://lists.grok.org.uk/pipermail/full-disclosure/2007-November/058576.html
- http://osvdb.org/40801
- http://secunia.com/advisories/27714
- http://secunia.com/advisories/28310
- http://securityreason.com/securityalert/3375
- http://trac.wordpress.org/ticket/5367
- http://www.cl.cam.ac.uk/~sjm217/advisories/wordpress-cookie-auth.txt
- http://www.securityfocus.com/archive/1/483927/100/0/threaded
- http://www.securitytracker.com/id?1018980
- http://www.vupen.com/english/advisories/2007/3941
- https://exchange.xforce.ibmcloud.com/vulnerabilities/38578
- https://www.redhat.com/archives/fedora-package-announce/2008-January/msg00079.html
- https://www.redhat.com/archives/fedora-package-announce/2008-January/msg00098.html
- http://lists.grok.org.uk/pipermail/full-disclosure/2007-November/058576.html
- http://osvdb.org/40801
- http://secunia.com/advisories/27714
- http://secunia.com/advisories/28310
- http://securityreason.com/securityalert/3375
- http://trac.wordpress.org/ticket/5367
- http://www.cl.cam.ac.uk/~sjm217/advisories/wordpress-cookie-auth.txt
- http://www.securityfocus.com/archive/1/483927/100/0/threaded
- http://www.securitytracker.com/id?1018980
- http://www.vupen.com/english/advisories/2007/3941
- https://exchange.xforce.ibmcloud.com/vulnerabilities/38578
- https://www.redhat.com/archives/fedora-package-announce/2008-January/msg00079.html