CVE-2010-4365 json
SQL injection vulnerability in JE Ajax Event Calendar (com_jeajaxeventcalendar) component for Joomla!
published 15y ago modified 4mo ago also EUVD-2010-4334
- 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 62%
- public exploits
- 2
- Exploit-DB
Summary
SQL injection vulnerability in JE Ajax Event Calendar (com_jeajaxeventcalendar) component for Joomla! allows remote attackers to execute arbitrary SQL commands via the event_id parameter in an alleventlist_more action to index.php.
Is CVE-2010-4365 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-13997)
- Published
Exploit prediction
0.98% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-15610 Joomla! Component JE Ajax Event Calendar - SQL Injection webapps, 2010-11-25
- EDB-13997 Joomla! Component JE Ajax Event Calendar 1.0.5 - SQL Injection webapps, 2010-06-23
- packetstormsecurity.org http://packetstormsecurity.org/files/view/96125/joomlaajax-sql.txt referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/45050 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/15610
exploit
-
packetstormsecurity.org
/files/view/96125/joomlaajax-sql.txt
exploit
-
securityfocus.com
/bid/45050
vdb-entry, exploit
-
secunia.com
/advisories/39836
third-party-advisory, vendor-advisory
Sources
- CVE List CVE-2010-4365
- NVD CVE-2010-4365
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.