CVE-2010-5036 json
SQL injection vulnerability in addsale.php in iScripts eSwap 2.0 allows remote attackers to execute arbitrary SQL commands via the type par…
published 15y ago modified 4mo ago also EUVD-2010-5000
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 67%
- public exploits
- 1
- Exploit-DB
Summary
SQL injection vulnerability in addsale.php in iScripts eSwap 2.0 allows remote attackers to execute arbitrary SQL commands via the type parameter.
Is CVE-2010-5036 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-13740)
- Published
Exploit prediction
1.15% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-13740 iScripts eSwap 2.0 - SQL Injection / Cross-Site Scripting webapps, 2010-06-06
- packetstormsecurity.org http://packetstormsecurity.org/1006-exploits/iscriptsewap-sqlxss.txt referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/40597 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
exploit-db.com
/exploits/13740/
exploit
-
packetstormsecurity.org
/1006-exploits/iscriptsewap-sqlxss.txt
exploit
-
securityfocus.com
/bid/40597
vdb-entry, exploit
-
vupen.com
/english/advisories/2010/1360
vdb-entry, vendor-advisory
-
securityreason.com
/securityalert/8522
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/59147
vdb-entry
Sources
- CVE List CVE-2010-5036
- NVD CVE-2010-5036
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.