# CVE-2008-2638: Code injection in n/a

> Remote attackers can execute arbitrary PHP code by injecting malicious input into the guestbook message field, compromising the web server.

- **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:** 10 Jun 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-23r2-7v4m-m7mp

## What is CVE-2008-2638?

CVE-2008-2638 is a critical code injection vulnerability in n/a, published on 10 Jun 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Static code injection vulnerability in guestbook.php in 1Book 1.0.1 and earlier allows remote attackers to upload arbitrary PHP code via the message parameter in an HTML webform, which is written to data.php.

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

## Which versions are affected by CVE-2008-2638?

It affects 1 product.


Products: 1-Script 1-Book.

## How do I fix CVE-2008-2638?

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

## Is CVE-2008-2638 being exploited?

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

Public exploit code:

- 1Book Guestbook Script 1.0.1 - Code Execution (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-2638 and fix it if it is affected.

What it is: CVE-2008-2638 is a critical code injection vulnerability in n/a, published on 10 Jun 2008. 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-2008-2638 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-2008-2638/ (Markdown: https://insights.sbomify.com/CVE-2008-2638/index.md)
```

## Sources

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

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