CVE-2006-3101 json
Cross-site scripting (XSS) vulnerability in LogonProxy.cgi in Cisco Secure ACS for UNIX 2.3 allows remote attackers to inject arbitrary web…
published 2006-06-21 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-3098
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 24.0%
- EPSS 24.0% chance of exploitation in 30 days, percentile 97%
- public exploits
- 1
- Exploit-DB
Summary
Cross-site scripting (XSS) vulnerability in LogonProxy.cgi in Cisco Secure ACS for UNIX 2.3 allows remote attackers to inject arbitrary web script or HTML via the (1) error, (2) SSL, and (3) Ok parameters.
Patch / fix
Timeline
- First public exploit (EDB-28030)
- Published
Exploit prediction
24.00% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-28030 Cisco Secure ACS 2.3 - 'LoginProxy.cgi' Cross-Site Scripting remote, 2006-06-15
- securitytracker.com http://securitytracker.com/id?1016317 referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/18449 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
-
cisco.com
/en/US/products/sw/secursw/ps4911/tsd_products_security_response09186a00806b8bdb.html
vendor-advisory, patch
-
secunia.com
/advisories/20699
third-party-advisory, patch, vendor-advisory
-
securitytracker.com
/id?1016317
vdb-entry, exploit, patch
-
securityfocus.com
/bid/18449
vdb-entry, exploit, patch
-
exchange.xforce.ibmcloud.com
/vulnerabilities/27166
vdb-entry
-
securityfocus.com
/archive/1/437480/100/0/threaded
mailing-list
-
securityfocus.com
/archive/1/437441/100/0/threaded
mailing-list
-
osvdb.org
/26531
vdb-entry
-
vupen.com
/english/advisories/2006/2384
vdb-entry
-
securityreason.com
/securityalert/1116
third-party-advisory
Sources
- CVE List CVE-2006-3101
- NVD CVE-2006-3101
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.