# 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".


- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3f6p-75g4-52mx

## What is CVE-2006-0874?

CVE-2006-0874 is a critical vulnerability in n/a, published on 24 Feb 2006. 

### Official description

Multiple unspecified vulnerabilities in Intensive Point iUser Ecommerce before 2.2 have unspecified vectors and impact, as addressed by "Urgent secure fixes".  NOTE: this might be a duplicate of CVE-2006-0854, but the vendor announcement for this issue (from January 8, 2005) is too vague to be sure, and CVE-2006-0854 does not provide version information.

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

It affects 1 product.


Products: Intensive Point Iuser Ecommerce.

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

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

## Is CVE-2006-0874 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-0854](https://insights.sbomify.com/CVE-2006-0854/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0874 is a critical vulnerability in n/a, published on 24 Feb 2006. 
Exploitation: There is no known exploitation of CVE-2006-0874 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-0874/ (Markdown: https://insights.sbomify.com/CVE-2006-0874/index.md)
```

## Sources

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

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