# CVE-2006-3267: SQL injection vulnerability in index.php in Infinite Core Technologies (ICT) 1.0 Gold and earlier allows remote attackers to execute arbitra


- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Jun 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hchp-79vp-qc9m

## What is CVE-2006-3267?

CVE-2006-3267 is a high-severity vulnerability in n/a, published on 27 Jun 2006. 

### Official description

SQL injection vulnerability in index.php in Infinite Core Technologies (ICT) 1.0 Gold and earlier allows remote attackers to execute arbitrary SQL commands via the post parameter.

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

It affects 1 product.


Products: Infinite Core Technologies Ict.

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

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

## Is CVE-2006-3267 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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