CVE-2005-3366 json
PHP file inclusion vulnerability in index.php in PHP iCalendar 2.0a2 through 2.0.1 allows remote attackers to execute arbitrary PHP code an…
published 2005-10-29 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-3365
- cvss
- 6.8
- 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
- 0
- none known
Summary
PHP file inclusion vulnerability in index.php in PHP iCalendar 2.0a2 through 2.0.1 allows remote attackers to execute arbitrary PHP code and include arbitrary local files via the phpicalendar cookie. NOTE: this is not a cross-site scripting (XSS) issue as claimed by the original researcher.
Patch / fix
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
- ush.it http://www.ush.it/2005/10/25/php-icalendar-css/ referenced PoC, tagged "exploit" by a source, unverified
- archives.neohapsis.com http://archives.neohapsis.com/archives/fulldisclosure/2005-10/0512.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
References
-
ush.it
/2005/10/25/php-icalendar-css/
exploit, patch, vendor-advisory
-
archives.neohapsis.com
/archives/fulldisclosure/2005-10/0512.html
mailing-list, exploit, patch, vendor-advisory
-
secunia.com
/advisories/17328/
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2005/2204
vdb-entry
-
securityreason.com
/securityalert/113
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/22864
vdb-entry
-
marc.info
/?l=bugtraq&m=113025930517426&w=2
mailing-list
-
securityfocus.com
/bid/15193
vdb-entry
-
securitytracker.com
/id?1015102
vdb-entry
Sources
- CVE List CVE-2005-3366
- NVD CVE-2005-3366
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.