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

> Remote authenticated administrators can inject arbitrary PHP code into the footer configuration, potentially leading to code execution.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cwrj-9f27-p9c8

## What is CVE-2009-0251?

CVE-2009-0251 is a medium-severity code injection vulnerability in n/a, published on 22 Jan 2009. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Static code injection vulnerability in admin.php in Ryneezy phoSheezy 0.2 allows remote authenticated administrators to inject arbitrary PHP code into config/footer via the footer parameter.  NOTE: this can be exploited by unauthenticated attackers by leveraging CVE-2009-0250. NOTE: some of these details are obtained from third party information.

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

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

It affects 1 product.


Products: Ryneezy Phosheezy.

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

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

## Is CVE-2009-0251 being exploited?

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

Public exploit code:

- phosheezy 2.0 - Remote Command Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-0275](https://insights.sbomify.com/CVE-2009-0275/): Code injection in n/a (medium 6.5)
- [CVE-2009-0250](https://insights.sbomify.com/CVE-2009-0250/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-0251 is a medium-severity code injection vulnerability in n/a, published on 22 Jan 2009. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-0251 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-0251/ (Markdown: https://insights.sbomify.com/CVE-2009-0251/index.md)
```

## Sources

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

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