CVE-2011-3128: Infoleak
First published: Wed Aug 10 2011(Updated: )
WordPress 3.1 before 3.1.3 and 3.2 before Beta 2 treats unattached attachments as published, which might allow remote attackers to obtain sensitive data via vectors related to wp-includes/post.php.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WordPress | =3.1 | |
| WordPress | =3.2-beta1 | |
| WordPress | =3.1.2 | |
| WordPress | =3.1.1 |
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-2011-3128?
CVE-2011-3128 is classified as a medium severity vulnerability.
How do I fix CVE-2011-3128?
To resolve CVE-2011-3128, you should update your WordPress to version 3.1.3 or later.
What versions of WordPress are affected by CVE-2011-3128?
CVE-2011-3128 affects WordPress versions 3.1, 3.1.1, 3.1.2, and 3.2 Beta 1.
What kind of attacks can exploit CVE-2011-3128?
CVE-2011-3128 can be exploited to allow remote attackers to access sensitive data from unattached attachments.
Is CVE-2011-3128 still a risk today?
While CVE-2011-3128 may no longer be a risk for users of current WordPress versions, outdated installations remain vulnerable.
- agent/references
- agent/type
- agent/remedy
- agent/softwarecombine
- agent/author
- agent/severity
- agent/weakness
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-historical
- agent/software-canonical-lookup-request
- collector/nvd-index
- vendor/wordpress
- canonical/wordpress
- version/wordpress/3.1
- version/wordpress/3.2-beta1
- version/wordpress/3.1.2
- version/wordpress/3.1.1