# CVE-2009-4315: Path traversal in n/a

> Remote attackers can execute arbitrary PHP code by exploiting a directory traversal flaw in Nuggetz CMS when magic_quotes_gpc is disabled.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Dec 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pjfm-7x3f-qhfp

## What is CVE-2009-4315?

CVE-2009-4315 is a medium-severity path traversal vulnerability in n/a, published on 14 Dec 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in admin/ajaxsave.php in Nuggetz CMS 1.0, when magic_quotes_gpc is disabled, allows remote attackers to create or modify arbitrary files via a .. (dot dot) in the nugget parameter and a modified pagevalue parameter, as demonstrated by creating and accessing a .php file to execute arbitrary PHP code.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Nuggetz Nuggetz Cms.

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

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

## Is CVE-2009-4315 being exploited?

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

Public exploit code:

- Nuggetz CMS 1.0 - Remote Code Execution (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-4315 is a medium-severity path traversal vulnerability in n/a, published on 14 Dec 2009. Any signed-in user can exploit it 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-4315 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-4315/ (Markdown: https://insights.sbomify.com/CVE-2009-4315/index.md)
```

## Sources

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

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