Skip to content
Fencer Intel
medium 4.3

CVE-2009-4433 json

Multiple cross-site scripting (XSS) vulnerabilities in IDevSpot iSupport 1.8 and earlier allow remote attackers to inject arbitrary web scr…

published 16y ago modified 4mo ago also EUVD-2009-4400

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
3
Exploit-DB

Summary

Multiple cross-site scripting (XSS) vulnerabilities in IDevSpot iSupport 1.8 and earlier allow remote attackers to inject arbitrary web script or HTML via the (a) 5 or (b) 9 field in a post action to ticket_function.php, reachable through ticket_submit.php and index.php; (c) the which parameter to function.php, or (d) the which parameter to index.php, related to knowledgebase_list.php. NOTE: some of these details are obtained from third party information.

Is CVE-2009-4433 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (EDB-33412)
  2. Published

Exploit prediction

2.24% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-33412 iSupport 1.8 - 'index.php?which' Cross-Site Scripting webapps, 2009-12-16
  • EDB-33411 iSupport 1.8 - 'ticket_function.php' Multiple Cross-Site Scripting Vulnerabilities webapps, 2009-12-16
  • EDB-10478 iSupport 1.8 - Cross-Site Scripting / Local File Inclusion webapps, 2009-12-16
  • packetstormsecurity.org http://packetstormsecurity.org/0912-exploits/isupport-lfixss.txt referenced PoC, tagged "exploit" by a source, unverified
  • securityfocus.com http://www.securityfocus.com/bid/37380 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

Sources

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.