CVE-2009-4099 json
SQL injection vulnerability in the Google Calendar GCalendar (com_gcalendar) component 1.1.2, 2.1.4, and possibly earlier versions for Joom…
published 2009-11-28 16 y ago modified 2026-06-16 4 mo ago also EUVD-2009-4070
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 1
- Exploit-DB
Summary
SQL injection vulnerability in the Google Calendar GCalendar (com_gcalendar) component 1.1.2, 2.1.4, and possibly earlier versions for Joomla! allows remote attackers to execute arbitrary SQL commands via the gcid parameter. NOTE: some of these details are obtained from third party information.
Timeline
- First public exploit (EDB-10232)
- Published
Exploit prediction
2.31% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-10232 Joomla! Component com_gcalendar 1.1.2 - 'gcid' SQL Injection webapps, 2009-11-25
- packetstormsecurity.org http://packetstormsecurity.org/0911-exploits/joomlagcalendar-sql.txt referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/37141 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
-
packetstormsecurity.org
/0911-exploits/joomlagcalendar-sql.txt
exploit
-
securityfocus.com
/bid/37141
vdb-entry, exploit
-
secunia.com
/advisories/37476
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/54450
vdb-entry
-
securityfocus.com
/bid/37134
vdb-entry
-
osvdb.org
/60517
vdb-entry
Sources
- CVE List CVE-2009-4099
- NVD CVE-2009-4099
Fencer Vulns 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.