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

> Remote attackers can execute arbitrary PHP code in phpSkelSite via a malicious URL in the theme parameter when specific PHP configurations are enabled.

- **Severity:** Medium 5.1 (`AV:N/AC:H/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:** 16 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-crvg-x5wh-vfgr

## What is CVE-2009-0595?

CVE-2009-0595 is a medium-severity code injection vulnerability in n/a, published on 16 Feb 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 skysilver/login.tpl.php in phpSkelSite 1.4, when register_globals is enabled and magic_quotes_gpc is disabled, allows remote attackers to execute arbitrary PHP code via a URL in the theme parameter.

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

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

It affects 1 product.


Products: Phpskelsite Phpskelsite.

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

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

## Is CVE-2009-0595 being exploited?

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

Public exploit code:

- phpskelsite 1.4 - Local File Inclusion / Remote File Inclusion / Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-0596](https://insights.sbomify.com/CVE-2009-0596/): Path traversal in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-0595 is a medium-severity code injection vulnerability in n/a, published on 16 Feb 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-0595 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-0595/ (Markdown: https://insights.sbomify.com/CVE-2009-0595/index.md)
```

## Sources

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

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