CVE-2010-2153 json
Unrestricted file upload vulnerability in admin/code/tce_functions_tcecode_editor.php in TCExam 10.1.006 and 10.1.007 allows remote attacke…
published 2010-06-03 16 y ago modified 2026-06-16 4 mo ago also EUVD-2010-2169
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.5%
- EPSS 7.5% chance of exploitation in 30 days, percentile 94%
- public exploits
- 1
- Exploit-DB
Summary
Unrestricted file upload vulnerability in admin/code/tce_functions_tcecode_editor.php in TCExam 10.1.006 and 10.1.007 allows remote attackers to execute arbitrary code by uploading a file with an executable extension, then accessing it via a direct request to the file in cache/.
Timeline
- First public exploit (EDB-34073)
- Published
Exploit prediction
7.47% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-34073 TCExam 10.1.7 - '/admin/code/tce_functions_tcecode_editor.php' Arbitrary File Upload webapps, 2010-06-02
- securityfocus.com http://www.securityfocus.com/bid/40511 referenced PoC, tagged "exploit" by a source, unverified
- cross-site-scripting.blogspot.com http://cross-site-scripting.blogspot.com/2010/06/tcexam-101006-arbitrary-upload.html referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.org http://www.packetstormsecurity.org/1006-exploits/tcexam-shell.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
References
-
securityfocus.com
/bid/40511
vdb-entry, exploit
-
cross-site-scripting.blogspot.com
/2010/06/tcexam-101006-arbitrary-upload.html
exploit
-
packetstormsecurity.org
/1006-exploits/tcexam-shell.txt
exploit
-
secunia.com
/advisories/40011
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2010/1329
vdb-entry, vendor-advisory
-
osvdb.org
/65052
vdb-entry
Sources
- CVE List CVE-2010-2153
- NVD CVE-2010-2153
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.