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

> Remote attackers can read and modify arbitrary files in pheap via directory traversal in edit.php.

- **Severity:** Critical 9.4 (`AV:N/AC:L/Au:N/C:C/I:C/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wh5j-4rf7-c96f

## What is CVE-2007-1140?

CVE-2007-1140 is a critical path traversal vulnerability in n/a, published on 27 Feb 2007. It can be exploited over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in edit.php in pheap allows remote attackers to read and modify arbitrary files via a .. (dot dot) in the filename parameter.

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

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

It affects 1 product.


Products: Barekoncept Pheap.

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

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

## Is CVE-2007-1140 being exploited?

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

Public exploit code:

- Pheap 1.x/2.0 - 'edit.php' Directory Traversal (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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