CVE-2006-0568 json
Cross-site scripting (XSS) vulnerability in throw.main in Outblaze allows remote attackers to inject arbitrary web script or HTML via the f…
published 2006-02-07 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-0575
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
Cross-site scripting (XSS) vulnerability in throw.main in Outblaze allows remote attackers to inject arbitrary web script or HTML via the file parameter.
Exploit prediction
2.22% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- osvdb.org http://www.osvdb.org/22909 referenced PoC, tagged "exploit" by a source, unverified
- morx.org http://www.morx.org/outblazeXSS.txt referenced PoC, tagged "exploit" by a source, unverified
- archives.neohapsis.com http://archives.neohapsis.com/archives/fulldisclosure/2006-02/0024.html referenced PoC, tagged "exploit" by a source, unverified
- secunia.com http://secunia.com/advisories/18710 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 |
References
-
osvdb.org
/22909
vdb-entry, exploit
-
morx.org
/outblazeXSS.txt
exploit, vendor-advisory
-
archives.neohapsis.com
/archives/fulldisclosure/2006-02/0024.html
mailing-list, exploit, vendor-advisory
-
secunia.com
/advisories/18710
third-party-advisory, exploit, vendor-advisory
-
vupen.com
/english/advisories/2006/0439
vdb-entry
-
securityreason.com
/securityalert/411
third-party-advisory
-
securityfocus.com
/archive/1/423915/100/0/threaded
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/24476
vdb-entry
Sources
- CVE List CVE-2006-0568
- NVD CVE-2006-0568
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.