CVE-2008-2640 json
Multiple cross-site scripting (XSS) vulnerabilities in the Flex 3 History Management feature in Adobe Flex 3.0.1 SDK and Flex Builder 3, an…
published 2008-06-18 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-2635
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.8%
- EPSS 2.8% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
Multiple cross-site scripting (XSS) vulnerabilities in the Flex 3 History Management feature in Adobe Flex 3.0.1 SDK and Flex Builder 3, and generated applications, allow remote attackers to inject arbitrary web script or HTML via the anchor identifier to (1) client-side-detection-with-history/history/historyFrame.html, (2) express-installation-with-history/history/historyFrame.html, or (3) no-player-detection-with-history/history/historyFrame.html in templates/html-templates/. NOTE: Firefox 2.0 and possibly other browsers prevent exploitation.
Patch / fix
Exploit prediction
2.77% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- blog.watchfire.com http://blog.watchfire.com/wfblog/2008/06/javascript-code.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
adobe.com
/support/security/bulletins/apsb08-14.html
patch
-
secunia.com
/advisories/30746
third-party-advisory, patch, vendor-advisory
-
securityfocus.com
/bid/29778
vdb-entry, patch
-
blog.watchfire.com
/wfblog/2008/06/javascript-code.html
exploit
-
securitytracker.com
/id?1020301
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/43150
vdb-entry
-
vupen.com
/english/advisories/2008/1862
vdb-entry
Sources
- CVE List CVE-2008-2640
- NVD CVE-2008-2640
Fencer Vulns 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.