# CVE-2007-2501: Eval injection vulnerability in codepress.html in CodePress before 0.9.4 allows remote attackers to execute arbitrary code via certain input


- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fp9p-v798-8f32

## What is CVE-2007-2501?

CVE-2007-2501 is a high-severity vulnerability in n/a, published on 4 May 2007. 

### Official description

Eval injection vulnerability in codepress.html in CodePress before 0.9.4 allows remote attackers to execute arbitrary code via certain input that is used in an eval function call.

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

It affects 1 product.


Products: Fernando M.a.d.s. Codepress.

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

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

## Is CVE-2007-2501 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-2501 is a high-severity vulnerability in n/a, published on 4 May 2007. 
Exploitation: There is no known exploitation of CVE-2007-2501 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-2501/ (Markdown: https://insights.sbomify.com/CVE-2007-2501/index.md)
```

## Sources

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

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