CVE-2005-4011 json
SQL injection vulnerability in calendar.php in Codewalkers ltwCalendar (aka PHP Event Calendar) 4.2, 4.1.3, and earlier allows remote attac…
published 2005-12-05 20 y ago modified 2026-06-16 4 mo ago also EUVD-2005-4006
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 83%
- public exploits
- 1
- Exploit-DB
Summary
SQL injection vulnerability in calendar.php in Codewalkers ltwCalendar (aka PHP Event Calendar) 4.2, 4.1.3, and earlier allows remote attackers to execute arbitrary SQL commands via the id parameter.
Timeline
- Published
- First public exploit (EDB-28088)
Exploit prediction
2.37% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-28088 PHP Event Calendar 4.2 - SQL Injection webapps, 2006-06-22
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
-
secunia.com
/advisories/17799
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2005/2652
vdb-entry, vendor-advisory
-
securitytracker.com
/id?1016364
vdb-entry
-
securityfocus.com
/archive/1/438580/100/0/threaded
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/27362
vdb-entry
-
osvdb.org
/27539
vdb-entry
-
attrition.org
/pipermail/vim/2006-December/001154.html
mailing-list
-
securityfocus.com
/bid/18593
vdb-entry
-
securityfocus.com
/bid/15636
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/23312
vdb-entry
-
osvdb.org
/21195
vdb-entry
- ltwcalendar.sourceforge.net /changelog.php
- silitix.com /calendar-cws.php
- pridels0.blogspot.com /2005/11/codewalkers-ltwcalendar-4x-sql-inj.html
-
securityfocus.com
/archive/1/438232/100/0/threaded
mailing-list
Sources
- CVE List CVE-2005-4011
- NVD CVE-2005-4011
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.