CVE-2011-3128
WordPress 3.1 before 3.1.3 and 3.2 before Beta 2 treats unattached attachments as published,...
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.
Exploit likelihood
What each source reports
NVD Score used
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.
- Record
CVE-2011-3128- CVSS 2.0
- 5.0 Medium
AV:N/AC:L/Au:N/C:P/I:N/A:N - Weakness
- CWE-200
- Updated
- 2026-11-02
CVE List No score
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.
- Record
CVE-2011-3128- Updated
- 2026-11-02
EUVDEUVD-2011-3096 No score
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.
- Record
EUVD-2011-3096- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-f5gx-hrrr-h7q3 No score
WordPress 3.1 before 3.1.3 and 3.2 before Beta 2 treats unattached attachments as published,...
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.
- Record
GHSA-f5gx-hrrr-h7q3- Weakness
- CWE-200
- Updated
- 2026-11-02
OSV No score
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.
- Record
CVE-2011-3128- Updated
- 2026-11-02
OSVDEBIAN-CVE-2011-3128 No score
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.
- Record
DEBIAN-CVE-2011-3128- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
wordpressDebian:12 |
before 3.2.1+dfsg-1 | 3.2.1+dfsg-1 |
wordpressDebian:13 |
before 3.2.1+dfsg-1 | 3.2.1+dfsg-1 |
wordpressDebian:14 |
before 3.2.1+dfsg-1 | 3.2.1+dfsg-1 |
wordpressDebian:6.0 From an advisory covering 15 CVEs |
before 3.3.2+dfsg-1~squeeze1, plus listed versions 3.0.4+dfsg-13.0.5+dfsg-0+squeeze13.0.5+dfsg-13.2.1+dfsg-13.2.1+dfsg-23.2.1+dfsg-33.3+dfsg-13.3.1+dfsg-1 |
3.3.2+dfsg-1~squeeze1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2011-3128 is a medium vulnerability (CVSS 5.0) in Wordpress, published August 10, 2011. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 2.45%, the 84th percentile. Fixed in wordpress 3.2.1+dfsg-1.
References
exchange.xforce.ibmcloud.com/vulnerabilities/69171
securityfocus.com/bid/47995
secunia.com/advisories/49138
wordpress.org/news/2011/05/wordpress-3-1-3
core.trac.wordpress.org/changeset/18023/branches/3.1
debian.org/security/2012/dsa-2470
nvd.nist.gov/vuln/detail/CVE-2011-3128
github.com/advisories/GHSA-f5gx-hrrr-h7q3
security-tracker.debian.org/tracker/CVE-2011-3128