# CVE-2009-0820: Code injection in n/a

> Remote attackers can execute arbitrary code via eval injection in phpScheduleIt scheduling application parameters.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Mar 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6vj2-4wv8-fm3g

## What is CVE-2009-0820?

CVE-2009-0820 is a high-severity code injection vulnerability in n/a, published on 5 Mar 2009. It can be exploited over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2009-0820?

It affects 1 product.


Products: Php.brickhost Phpscheduleit.

## How do I fix CVE-2009-0820?

No fix has been published for CVE-2009-0820 yet. Limit exposure of the affected software until one is available.

## Is CVE-2009-0820 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-0820 exists.

Public exploit code:

- phpScheduleIt 1.2.10 - 'reserve.php' Remote Code Execution (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0820 and fix it if it is affected.

What it is: CVE-2009-0820 is a high-severity code injection vulnerability in n/a, published on 5 Mar 2009. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-0820 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2009-0820/ (Markdown: https://insights.sbomify.com/CVE-2009-0820/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2009-0820
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2009-0820
- OSV: https://osv.dev/vulnerability/CVE-2009-0820

---
From sbomify Insights: https://insights.sbomify.com/CVE-2009-0820/
Summaries are generated and may contain mistakes; the official description above is the record.