CVE-2006-1230 json
Multiple cross-site scripting (XSS) vulnerabilities in create.php in vCard 2.x allow remote attackers to inject arbitrary web script or HTM…
published 2006-03-14 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-1234
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.6%
- EPSS 2.6% chance of exploitation in 30 days, percentile 85%
- public exploits
- 1
- Exploit-DB
Summary
Multiple cross-site scripting (XSS) vulnerabilities in create.php in vCard 2.x allow remote attackers to inject arbitrary web script or HTML via the (1) card_id, (2) uploaded, (3) card_fontsize, or (4) card_color parameter. NOTE: the card_id vector was later reported to affect vCard 2.9, and the uploaded vector for 2.6.
Timeline
- First public exploit (EDB-27414)
- Published
Exploit prediction
2.58% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-27414 vCard 2.8/2.9 - 'create.php' Multiple Cross-Site Scripting Vulnerabilities webapps, 2006-03-11
- securityfocus.com http://www.securityfocus.com/bid/17073 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
-
securityfocus.com
/bid/17073
vdb-entry, exploit
-
vupen.com
/english/advisories/2006/0945
vdb-entry, vendor-advisory
-
secunia.com
/advisories/19216
third-party-advisory, vendor-advisory
-
securitytracker.com
/id?1016183
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/25181
vdb-entry
-
osvdb.org
/23838
vdb-entry
-
securityfocus.com
/archive/1/427408/100/0/threaded
mailing-list
-
securityfocus.com
/archive/1/461922/100/0/threaded
mailing-list
-
securityfocus.com
/archive/1/435310/100/0/threaded
mailing-list
-
securityfocus.com
/bid/22819
vdb-entry
Sources
- CVE List CVE-2006-1230
- NVD CVE-2006-1230
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.