CVE-2010-2290 json
Cross-site scripting (XSS) vulnerability in cgi-bin/cgix/help in McAfee Unified Threat Management (UTM) Firewall (formerly SnapGear) firmwa…
published 2010-06-15 16 y ago modified 2026-06-16 4 mo ago also EUVD-2010-2300
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
Cross-site scripting (XSS) vulnerability in cgi-bin/cgix/help in McAfee Unified Threat Management (UTM) Firewall (formerly SnapGear) firmware 3.0.0 through 4.0.6 allows remote attackers to inject arbitrary web script or HTML via the page parameter.
Patch / fix
Exploit prediction
1.33% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- ngenuity-is.com http://ngenuity-is.com/advisories/2010/jun/9/mcafee-utm-firewall-help-cross-site-scripting/ referenced PoC, tagged "exploit" by a source, unverified
- securitytracker.com http://www.securitytracker.com/id?1024091 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
-
kc.mcafee.com
/corporate/index?page=content&id=SB10010
patch, vendor-advisory
-
ngenuity-is.com
/advisories/2010/jun/9/mcafee-utm-firewall-help-cross-site-scripting/
exploit
-
securitytracker.com
/id?1024091
vdb-entry, exploit
-
vupen.com
/english/advisories/2010/1413
vdb-entry, vendor-advisory
-
secunia.com
/advisories/40089
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/40138
third-party-advisory, vendor-advisory
-
securityfocus.com
/archive/1/511771/100/0/threaded
mailing-list
Sources
- CVE List CVE-2010-2290
- NVD CVE-2010-2290
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.