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

> Remote attackers can execute arbitrary code by exploiting a PHP remote file inclusion vulnerability in the iUser Ecommerce application.

- **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:** 23 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-x48h-jvv3-m642

## What is CVE-2006-0854?

CVE-2006-0854 is a high-severity code injection vulnerability in n/a, published on 23 Feb 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 common.php in Intensive Point iUser Ecommerce allows remote attackers to include arbitrary files via a URL in the include_path variable, which is not initialized before being used.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Intensive Point Iuser Ecommerce.

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

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

## Is CVE-2006-0854 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-0874](https://insights.sbomify.com/CVE-2006-0874/): Multiple unspecified vulnerabilities in Intensive Point iUser Ecommerce before 2.2 have unspecified vectors and impact, as addressed by "Urgent secure fixes". (critical 10.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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