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

> Remote attackers with admin privileges can inject and execute arbitrary PHP code via theme or configuration parameters in UBB.threads.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8gqx-3g5h-mh24

## What is CVE-2006-5137?

CVE-2006-5137 is a medium-severity code injection vulnerability in n/a, published on 2 Oct 2006. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Multiple direct static code injection vulnerabilities in Groupee UBB.threads 6.5.1.1 allow remote attackers to (1) inject PHP code via a theme[] array parameter to admin/doedittheme.php, which is injected into includes/theme.inc.php; (2) inject PHP code via a config[] array parameter to admin/doeditconfig.php, and then execute the code via includes/config.inc.php; and inject a reference to PHP code via a URL in the config[path] parameter, and then execute the code via (3) dorateuser.php, (4) calendar.php, and unspecified other scripts.

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

It affects 1 product.


Products: Ubbcentral Ubb.threads.

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

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

## Is CVE-2006-5137 being exploited?

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

Public exploit code:

- UBBCentral UBB.Threads 6.5.1.1 - 'doeditconfig.php' Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-6970](https://insights.sbomify.com/CVE-2008-6970/): SQL injection in n/a (high 7.5)
- [CVE-2007-1956](https://insights.sbomify.com/CVE-2007-1956/): SQL injection in n/a (high 7.5)
- [CVE-2006-5136](https://insights.sbomify.com/CVE-2006-5136/): Code injection in n/a (high 7.5)
- [CVE-2006-0545](https://insights.sbomify.com/CVE-2006-0545/): SQL injection in n/a (high 7.5)
- [CVE-2005-2058](https://insights.sbomify.com/CVE-2005-2058/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5137 is a medium-severity code injection vulnerability in n/a, published on 2 Oct 2006. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-5137 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-5137/ (Markdown: https://insights.sbomify.com/CVE-2006-5137/index.md)
```

## Sources

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

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