CVE-2010-4736 json
SQL injection vulnerability in ECO.asp in GateSoft DocuSafe 4.1.0 and 4.1.2 allows remote attackers to execute arbitrary SQL commands via t…
published 15y ago modified 4mo ago also EUVD-2010-4701
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 1
- Exploit-DB
Summary
SQL injection vulnerability in ECO.asp in GateSoft DocuSafe 4.1.0 and 4.1.2 allows remote attackers to execute arbitrary SQL commands via the ECO_ID parameter. NOTE: some of these details are obtained from third party information.
Is CVE-2010-4736 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-15686)
- Published
Exploit prediction
1.02% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-15686 Gatesoft Docusafe 4.1.0 - SQL Injection webapps, 2010-12-05
- packetstormsecurity.org http://packetstormsecurity.org/files/view/96398/gatesafedocusafe-sql.txt referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/45182 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/15686
exploit
-
packetstormsecurity.org
/files/view/96398/gatesafedocusafe-sql.txt
exploit
-
securityfocus.com
/bid/45182
vdb-entry, exploit
-
secunia.com
/advisories/27660
third-party-advisory, vendor-advisory
-
securityreason.com
/securityalert/8086
third-party-advisory
Sources
- CVE List CVE-2010-4736
- NVD CVE-2010-4736
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.