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

> Remote attackers can inject and execute arbitrary PHP code in WebText CMS by manipulating the im parameter during profile edits.

- **Severity:** High 7.5 (`AV:N/AC:L/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:** 4 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rjw6-23p4-j5pw

## What is CVE-2006-6856?

CVE-2006-6856 is a high-severity code injection vulnerability in n/a, published on 4 Jan 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Direct static code injection vulnerability in WebText CMS 0.4.5.2 and earlier allows remote attackers to inject arbitrary PHP code into a script in wt/users/ via the im parameter during a profile edit (edycja) operation, which is then executed via a direct request for this script.

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

It affects 1 product.


Products: Webtext Webtext.

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

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

## Is CVE-2006-6856 being exploited?

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

Public exploit code:

- WebText 0.4.5.2 - Remote Code Execution (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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