CVE-2011-3128 json
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 s…
published 2011-08-10 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-3096
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- wordpress Debian 14, Debian 13, Debian 12 3.2.1+dfsg-1
debian advisories DEBIAN-CVE-2011-3128
Exploit prediction
2.45% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Technology feeds
References
-
wordpress.org
/news/2011/05/wordpress-3-1-3/
patch
-
core.trac.wordpress.org
/changeset/18023/branches/3.1
patch
-
debian.org
/security/2012/dsa-2470
vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/69171
vdb-entry
-
securityfocus.com
/bid/47995
vdb-entry
-
secunia.com
/advisories/49138
third-party-advisory
Sources
- CVE List CVE-2011-3128
- NVD CVE-2011-3128
Fencer Intel 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.