CVE-2010-1336 json
Multiple SQL injection vulnerabilities in INVOhost 3.4 allow remote attackers to execute arbitrary SQL commands via the (1) id and (2) newl…
published 16y ago modified 4mo ago also EUVD-2010-1364
- 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 68%
- public exploits
- 1
- Exploit-DB
Summary
Multiple SQL injection vulnerabilities in INVOhost 3.4 allow remote attackers to execute arbitrary SQL commands via the (1) id and (2) newlanguage parameters to site.php, (3) search parameter to manuals.php, and (4) unspecified vectors to faq.php. NOTE: some of these details are obtained from third party information.
Is CVE-2010-1336 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-11874)
- Published
Exploit prediction
1.19% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-11874 INVOhost - SQL Injection webapps, 2010-03-25
- securityfocus.com http://www.securityfocus.com/bid/38962 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/11874
exploit
-
securityfocus.com
/bid/38962
vdb-entry, exploit
-
secunia.com
/advisories/39095
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/57161
vdb-entry
-
osvdb.org
/63157
vdb-entry
-
osvdb.org
/63158
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/57162
vdb-entry
Sources
- CVE List CVE-2010-1336
- NVD CVE-2010-1336
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.