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

> Remote attackers can execute arbitrary local files via directory traversal in Betsy CMS admin popup, risking code execution and data exposure.

- **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:** 24 Nov 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-596q-6pv4-cvww

## What is CVE-2009-4056?

CVE-2009-4056 is a high-severity path traversal vulnerability in n/a, published on 24 Nov 2009. It can be exploited over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in admin/popup.php in Betsy CMS 3.5 allows remote attackers to include and execute arbitrary local files via a .. (dot dot) in the popup parameter.

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

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

It affects 1 product.


Products: Betsy Betsy Cms.

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

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

## Is CVE-2009-4056 being exploited?

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

Public exploit code:

- Betsy CMS versions 3.5 - Local File Inclusion (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-4056 is a high-severity path traversal vulnerability in n/a, published on 24 Nov 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-4056 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-4056/ (Markdown: https://insights.sbomify.com/CVE-2009-4056/index.md)
```

## Sources

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

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