# CVE-2007-2985: Auth bypass in n/a

> Remote attackers can bypass authentication by manipulating a cookie to gain admin access, read passwords, and execute arbitrary code.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jun 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gjr5-xrxx-mv2c

## What is CVE-2007-2985?

CVE-2007-2985 is a critical authentication bypass vulnerability in n/a, published on 1 Jun 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pheap 2.0 allows remote attackers to bypass authentication by setting a pheap_login cookie value to the administrator's username, which can be used to (1) obtain sensitive information, including the administrator password, via settings.php or (2) upload and execute arbitrary PHP code via an update_doc action in edit.php.

Weakness: CWE-264

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

It affects 1 product.


Products: Pheap Pheap.

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

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

## Is CVE-2007-2985 being exploited?

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

Public exploit code:

- Pheap 2.0 - Authentication Bypass / Remote Code Execution (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-2985 is a critical authentication bypass vulnerability in n/a, published on 1 Jun 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-2985 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-2985/ (Markdown: https://insights.sbomify.com/CVE-2007-2985/index.md)
```

## Sources

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

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