CVE-2012-2400 in the critical feed json
Unspecified vulnerability in wp-includes/js/swfobject.js in WordPress before 3.3.2 has unknown impact and attack vectors.
published 2012-04-21 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-2387
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.1%
- EPSS 3.1% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in wp-includes/js/swfobject.js in WordPress before 3.3.2 has unknown impact and attack vectors.
Patch / fix
- wordpress Debian 14, Debian 13, Debian 12 3.3.2+dfsg-1
debian advisories DEBIAN-CVE-2012-2400
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2012-2400 updated cvss 4.3
v3.3.2): Unspecified vulnerability in the SWFObject
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
3.14% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Technology feeds
References
-
wordpress.org
/news/2012/04/wordpress-3-3-2/
patch, vendor-advisory
-
debian.org
/security/2012/dsa-2470
vendor-advisory
-
secunia.com
/advisories/49138
third-party-advisory
-
osvdb.org
/81460
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/75209
vdb-entry
- core.trac.wordpress.org /changeset/20499/branches/3.3/wp-includes/js/swfobject.js
-
securityfocus.com
/bid/53192
vdb-entry
Sources
- CVE List CVE-2012-2400
- NVD CVE-2012-2400
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.