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

> Remote attackers could execute arbitrary PHP code via URL injection in Amr Talkbox, though the vulnerability is disputed as the variable is static.

- **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:** 15 Jun 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rc3c-4c69-rjx6

## What is CVE-2006-3040?

CVE-2006-3040 is a high-severity vulnerability in n/a, published on 15 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 talkbox.php in Amr Talkbox allows remote attackers to execute arbitrary PHP code via a URL in the direct parameter.  NOTE: this issue has been disputed by CVE, since the $direct variable is set to a static value just before the include statement

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

It affects 1 product.


Products: Amr Talkbox Amr Talkbox.

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

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

## Is CVE-2006-3040 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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