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

> Remote attackers can execute arbitrary PHP code in Trawler Web CMS via remote file inclusion vulnerabilities in multiple scripts.

- **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:** 25 Oct 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8g9q-47ch-4vwh

## What is CVE-2006-5495?

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

### Official description

Multiple PHP remote file inclusion vulnerabilities in Trawler Web CMS 1.8.1 and earlier allow remote attackers to execute arbitrary PHP code via a URL in the (1) path_red2 parameter to (a) _msdazu_pdata/redaktion/artikel/up/index.php; (b) addtort.php, (c) colorpik2.php, (d) colorpik3.php, (e) extras_menu.php, (f) farbpalette.php, (g) lese_inc.php, and (h) newfile.php in _msdazu_share/richtext/; the (2) path_scr_dat2 parameter to (i)_msdazu_share/share/insert1.php; the (3) path_red parameter to (j) _msdazu_share/extras/downloads/index.php; and unspecified parameters in other files.

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

It affects 1 product.


Products: Trawler Trawler Web Cms.

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

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

## Is CVE-2006-5495 being exploited?

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

Public exploit code:

- Trawler Web CMS 1.8.1 - Multiple Remote File Inclusions (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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