CVE-2010-4945 json
SQL injection vulnerability in the CamelcityDB (com_camelcitydb2) component 2.2 for Joomla!
published 2011-10-09 15 y ago modified 2026-06-16 4 mo ago also EUVD-2010-4909
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 1
- Exploit-DB
Summary
SQL injection vulnerability in the CamelcityDB (com_camelcitydb2) component 2.2 for Joomla! allows remote attackers to execute arbitrary SQL commands via the id parameter to index.php.
Timeline
- First public exploit (EDB-14530)
- Published
Exploit prediction
1.31% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-14530 Joomla! Component CamelcityDB 2.2 - SQL Injection webapps, 2010-08-02
- securityfocus.com http://www.securityfocus.com/bid/33254 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.org http://packetstormsecurity.org/1008-exploits/joomlacamelcitydb2-sql.txt referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.org http://packetstormsecurity.org/0901-exploits/joomlacamel-sql.txt 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/14530
exploit
-
securityfocus.com
/bid/33254
vdb-entry, exploit
-
packetstormsecurity.org
/1008-exploits/joomlacamelcitydb2-sql.txt
exploit
-
packetstormsecurity.org
/0901-exploits/joomlacamel-sql.txt
exploit
-
securityreason.com
/securityalert/8465
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/60860
vdb-entry
Sources
- CVE List CVE-2010-4945
- NVD CVE-2010-4945
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.