# CVE-2006-3609: Cross-site scripting (XSS) vulnerability in index.php in Orbitcoders OrbitMATRIX 1.0 allows remote attackers to inject arbitrary web script


- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 14 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fqqj-4xfg-gp9g

## What is CVE-2006-3609?

CVE-2006-3609 is a medium-severity vulnerability in n/a, published on 14 Jul 2006. 

### Official description

Cross-site scripting (XSS) vulnerability in index.php in Orbitcoders OrbitMATRIX 1.0 allows remote attackers to inject arbitrary web script or HTML via the page_name parameter with an IMG tag containing a javascript URI in the SRC attribute.

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

It affects 1 product.


Products: Orbitcoders Orbitmatrix.

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

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

## Is CVE-2006-3609 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-3614](https://insights.sbomify.com/CVE-2006-3614/): SQL injection in n/a (high 7.5)
- [CVE-2006-3610](https://insights.sbomify.com/CVE-2006-3610/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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