CVE-2010-4837 json
Cross-site scripting (XSS) vulnerability in the JSupport (com_jsupport) component 1.5.6 for Joomla!
published 15y ago modified 4mo ago also EUVD-2010-4802
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 74%
- public exploits
- 1
- Exploit-DB
Summary
Cross-site scripting (XSS) vulnerability in the JSupport (com_jsupport) component 1.5.6 for Joomla! allows remote attackers to inject arbitrary web script or HTML via the subject parameter (title field) in a saveTicket action to index2.php. NOTE: some of these details are obtained from third party information.
Is CVE-2010-4837 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 FencerTimeline
- First public exploit (EDB-15501)
- Published
Exploit prediction
1.53% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-15501 Joomla! Component JSupport 1.5.6 - Cross-Site Scripting webapps, 2010-11-12
- xenuser.org http://www.xenuser.org/documents/security/Joomla_com_jsupport_XSS.txt referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.org http://packetstormsecurity.org/files/view/95796/joomlajsupport-xss.txt 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
-
exploit-db.com
/exploits/15501
exploit
-
xenuser.org
/documents/security/Joomla_com_jsupport_XSS.txt
exploit
-
packetstormsecurity.org
/files/view/95796/joomlajsupport-xss.txt
exploit
-
secunia.com
/advisories/42262
third-party-advisory, vendor-advisory
-
securityreason.com
/securityalert/8377
third-party-advisory
Sources
- CVE List CVE-2010-4837
- NVD CVE-2010-4837
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.