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

> Remote attackers can execute arbitrary PHP code via file inclusion if register_globals is enabled, though the vulnerability is disputed.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jgcq-72j8-f5wg

## What is CVE-2006-3069?

CVE-2006-3069 is a high-severity vulnerability in n/a, published on 19 Jun 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHP remote file inclusion vulnerability in DoubleSpeak 0.1, when register_globals is enabled, allows remote attackers to execute arbitrary PHP code via the config[private] parameter in multiple files, as demonstrated by (1) index.php, (2) faq.php, and (3) hardware.php. NOTE: this issue has been disputed by multiple third-party researchers, who state that config[private] is initialized in an include file before being used

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

It affects 1 product.


Products: Iglooweb Doublespeak.

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

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

## Is CVE-2006-3069 being exploited?

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

Public exploit code:

- DoubleSpeak 0.1 - Multiple Remote File Inclusions (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-3069 is a high-severity vulnerability in n/a, published on 19 Jun 2006. 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-2006-3069 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-3069/ (Markdown: https://insights.sbomify.com/CVE-2006-3069/index.md)
```

## Sources

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

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