# CVE-2007-2105: Path traversal in n/a

> Remote attackers can execute arbitrary local files via path traversal in the admin skin parameter, requiring administrative access.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/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:** 18 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vv6p-4rgx-3484

## What is CVE-2007-2105?

CVE-2007-2105 is a high-severity path traversal vulnerability in n/a, published on 18 Apr 2007. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Directory traversal vulnerability in admin/index.php in Monkey CMS 0.0.3 allows remote attackers to include and execute arbitrary local files via a .. (dot dot) in the admin_skin parameter.

## Which versions are affected by CVE-2007-2105?

It affects 1 product.


Products: Monkey Cms Monkey Cms.

## How do I fix CVE-2007-2105?

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

## Is CVE-2007-2105 being exploited?

There is no known exploitation of CVE-2007-2105 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2105 and fix it if it is affected.

What it is: CVE-2007-2105 is a high-severity path traversal vulnerability in n/a, published on 18 Apr 2007. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-2105 in the wild and no public exploit code.

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-2007-2105/ (Markdown: https://insights.sbomify.com/CVE-2007-2105/index.md)
```

## Sources

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

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