# CVE-2007-4290: Code injection in n/a

> Remote attackers can execute arbitrary PHP code via remote file inclusion in Guestbook Script, though the vulnerability is disputed by third parties.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Aug 2007
- **Updated:** 17 Jan 2025
- **Also known as:** GHSA-5wgh-3393-wp4p

## What is CVE-2007-4290?

CVE-2007-4290 is a critical code injection vulnerability in n/a, published on 9 Aug 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple PHP remote file inclusion vulnerabilities in Guestbook Script 1.9 allow remote attackers to execute arbitrary PHP code via a URL in the script_root parameter to (1) delete.php, (2) edit.php, or (3) inc/common.inc.php; or (4) database.php, (5) entries.php, (6) index.php, (7) logout.php, or (8) settings.php in admin/.  NOTE: a third party disputes this vulnerability, noting that these scripts defend against direct requests

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Stadtaus Guestbook Script.

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

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

## Is CVE-2007-4290 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-2158](https://insights.sbomify.com/CVE-2006-2158/): Code injection in n/a (medium 6.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-4290 is a critical code injection vulnerability in n/a, published on 9 Aug 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-4290 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-4290/ (Markdown: https://insights.sbomify.com/CVE-2007-4290/index.md)
```

## Sources

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

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