# CVE-2006-4788: File upload in n/a

> Remote attackers can execute arbitrary PHP code via a URL in the dir_path parameter if register_globals is enabled and specific session permissions are set.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6hmv-ffm8-2f8m

## What is CVE-2006-4788?

CVE-2006-4788 is a medium-severity vulnerability in n/a, published on 14 Sep 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PHP remote file inclusion vulnerability in includes/log.inc.php in Telekorn SignKorn Guestbook (SL) 1.3 and earlier, when register_globals is enabled and _SESSION[permission] parameter is set to "yes", allows remote attackers to execute arbitrary PHP code via a URL in the dir_path parameter.

## Which versions are affected by CVE-2006-4788?

It affects 1 product.


Products: Telekorn Signkorn Guestbook.

## How do I fix CVE-2006-4788?

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

## Is CVE-2006-4788 being exploited?

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

Public exploit code:

- Telekorn Signkorn Guestbook 1.3 - 'dir_path' Remote File Inclusion (exploitdb)

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4788 and fix it if it is affected.

What it is: CVE-2006-4788 is a medium-severity vulnerability in n/a, published on 14 Sep 2006. Any signed-in user can exploit it 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-2006-4788 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-2006-4788/ (Markdown: https://insights.sbomify.com/CVE-2006-4788/index.md)
```

## Sources

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

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