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

> Remote attackers can read arbitrary files and list directories via path traversal in the nfolder parameter of this PHP application.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3mpc-j5x7-cjc8

## What is CVE-2007-1138?

CVE-2007-1138 is a medium-severity path traversal vulnerability in n/a, published on 27 Feb 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Absolute path traversal vulnerability in list_main_pages.php in Cromosoft Simple Plantilla PHP (SPP) allows remote attackers to list arbitrary directories, and read arbitrary files, via an absolute pathname in the nfolder parameter.

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

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

It affects 1 product.


Products: Cromosoft Simple Plantilla Php.

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

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

## Is CVE-2007-1138 being exploited?

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

Public exploit code:

- Plantilla - 'list_main_pages.php?nfolder' Traversal Arbitrary File Access (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-1139](https://insights.sbomify.com/CVE-2007-1139/): File upload in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-1138 is a medium-severity path traversal vulnerability in n/a, published on 27 Feb 2007. 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-2007-1138 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-2007-1138/ (Markdown: https://insights.sbomify.com/CVE-2007-1138/index.md)
```

## Sources

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

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