CVE-2009-0820 json
Multiple eval injection vulnerabilities in phpScheduleIt before 1.2.11 allow remote attackers to execute arbitrary code via (1) the end_dat…
published 2009-03-05 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-0817
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.9%
- EPSS 4.9% chance of exploitation in 30 days, percentile 92%
- public exploits
- 1
- Exploit-DB
Summary
Multiple eval injection vulnerabilities in phpScheduleIt before 1.2.11 allow remote attackers to execute arbitrary code via (1) the end_date parameter to reserve.php and (2) the start_date and end_date parameters to check.php. NOTE: the start_date/reserve.php vector is already covered by CVE-2008-6132.
Patch / fix
- sourceforge.net/project/shownotes.php?release_id=662749 patch
- phpscheduleit.svn.sourceforge.net/viewvc/phpscheduleit/1.2.11/reserve.php?r1=318&r2=328 advisory
- vupen.com/english/advisories/2009/0491 advisory
- phpscheduleit.svn.sourceforge.net/viewvc/phpscheduleit/1.2.11/check.php?r1=318&r2=332 advisory
Timeline
- First public exploit (EDB-6646)
- Published
Exploit prediction
4.95% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-6646 phpScheduleIt 1.2.10 - 'reserve.php' Remote Code Execution webapps, 2008-10-01
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-94 Improper Control of Generation of Code
References
-
phpscheduleit.svn.sourceforge.net
/viewvc/phpscheduleit/1.2.11/reserve.php?r1=318&r2=328
patch, vendor-advisory
-
vupen.com
/english/advisories/2009/0491
vdb-entry, patch, vendor-advisory
-
phpscheduleit.svn.sourceforge.net
/viewvc/phpscheduleit/1.2.11/check.php?r1=318&r2=332
patch, vendor-advisory
-
sourceforge.net
/project/shownotes.php?release_id=662749
patch
-
secunia.com
/advisories/33991
third-party-advisory, vendor-advisory
Sources
- CVE List CVE-2009-0820
- NVD CVE-2009-0820
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.