CVE-2010-3602 json
Cross-site scripting (XSS) vulnerability in ProfileView.aspx in mojoPortal 2.3.4.3 and 2.3.5.1 allows remote attackers to inject arbitrary…
published 2010-09-24 16 y ago modified 2026-06-16 4 mo ago also EUVD-2010-3598
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.8%
- EPSS 3.8% chance of exploitation in 30 days, percentile 89%
- public exploits
- 1
- Exploit-DB
Summary
Cross-site scripting (XSS) vulnerability in ProfileView.aspx in mojoPortal 2.3.4.3 and 2.3.5.1 allows remote attackers to inject arbitrary web script or HTML via the User ID parameter. NOTE: some of these details are obtained from third party information.
Patch / fix
Timeline
- First public exploit (EDB-15018)
- Published
Exploit prediction
3.77% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-15018 mojoportal - Multiple Vulnerabilities webapps, 2010-09-16
- packetstormsecurity.org http://packetstormsecurity.org/1009-advisories/moaub16-mojoportal.pdf referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.org http://packetstormsecurity.org/1009-exploits/moaub-mojoportal.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
-
mojoportal.com
/mojoportal-2352-released.aspx
patch, vendor-advisory
-
exploit-db.com
/exploits/15018
exploit
-
packetstormsecurity.org
/1009-advisories/moaub16-mojoportal.pdf
exploit
-
packetstormsecurity.org
/1009-exploits/moaub-mojoportal.txt
exploit
-
secunia.com
/advisories/41481
third-party-advisory, vendor-advisory
-
securityfocus.com
/bid/43268
vdb-entry
-
osvdb.org
/68059
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/61835
vdb-entry
Sources
- CVE List CVE-2010-3602
- NVD CVE-2010-3602
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.