# CVE-2006-6790: Code injection in n/a

> Remote attackers can inject arbitrary PHP code via the username parameter in Ultimate PHP Board, leading to code execution.

- **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:** 28 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f287-8pwc-7x7r

## What is CVE-2006-6790?

CVE-2006-6790 is a high-severity code injection vulnerability in n/a, published on 28 Dec 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Direct static code injection vulnerability in chat/login.php in Ultimate PHP Board (UPB) 2.0b1 and earlier allows remote attackers to inject arbitrary PHP code via the username parameter, which is injected into chat/text.php.

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

It affects 1 product.


Products: Ultimate Php Board Ultimate Php Board.

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

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

## Is CVE-2006-6790 being exploited?

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

Public exploit code:

- Ultimate PHP Board 2.0b1 - '/chat/login.php' Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-3203](https://insights.sbomify.com/CVE-2006-3203/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2005-1615](https://insights.sbomify.com/CVE-2005-1615/): SQL injection in n/a (high 7.5)
- [CVE-2005-1616](https://insights.sbomify.com/CVE-2005-1616/): Information disclosure in n/a (high 7.5)
- [CVE-2006-7169](https://insights.sbomify.com/CVE-2006-7169/): Code injection in n/a (medium 6.8)
- [CVE-2005-1614](https://insights.sbomify.com/CVE-2005-1614/): Cross-site scripting in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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