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

> Remote attackers can execute arbitrary PHP code or include local files via the page parameter in School Data Navigator.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jul 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-963v-cpjr-8g28

## What is CVE-2009-2641?

CVE-2009-2641 is a medium-severity code injection vulnerability in n/a, published on 28 Jul 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHP remote file inclusion vulnerability in app_and_readme/navigator/index.php in School Data Navigator allows remote attackers to execute arbitrary PHP code via a URL in the page parameter.  NOTE: this can also be leveraged to include and execute arbitrary local files via .. (dot dot) sequences.

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

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

It affects 1 product.


Products: Rich White School Data Nav.

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

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

## Is CVE-2009-2641 being exploited?

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

Public exploit code:

- School Data Navigator - 'page' Local/Remote File Inclusion (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-2641 is a medium-severity code injection vulnerability in n/a, published on 28 Jul 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-2641 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-2641/ (Markdown: https://insights.sbomify.com/CVE-2009-2641/index.md)
```

## Sources

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

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