CVE-2012-5868: Infoleak
First published: Thu Dec 27 2012(Updated: )
WordPress 3.4.2 does not invalidate a wordpress_sec session cookie upon an administrator's logout action, which makes it easier for remote attackers to discover valid session identifiers via a brute-force attack, or modify data via a replay attack.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WordPress | =3.4.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2012-5868?
CVE-2012-5868 is classified as a medium severity vulnerability that could allow unauthorized access to valid session identifiers.
How do I fix CVE-2012-5868?
To fix CVE-2012-5868, upgrade to a version of WordPress later than 3.4.2 that addresses this session management issue.
What impact does CVE-2012-5868 have on my WordPress site?
CVE-2012-5868 makes it possible for attackers to exploit session identifiers, which could lead to unauthorized data modification or access.
Are all WordPress versions affected by CVE-2012-5868?
Only WordPress version 3.4.2 is specifically affected by CVE-2012-5868, as later versions include the necessary fixes.
What type of attacks can CVE-2012-5868 allow?
CVE-2012-5868 can potentially allow brute-force attacks to discover session identifiers and replay attacks to manipulate data.
- agent/type
- agent/softwarecombine
- agent/references
- agent/weakness
- agent/author
- agent/severity
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/wordpress
- canonical/wordpress
- version/wordpress/3.4.2