# CVE-2006-6510: Security feature bypass in n/a

> Local attackers can bypass security protections and read arbitrary files via an unsafe ActiveX control in SiteKiosk.

- **Severity:** Low 1.7 (`AV:L/AC:L/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wpwm-rpc6-hq6w

## What is CVE-2006-6510?

CVE-2006-6510 is a low-severity vulnerability in n/a, published on 14 Dec 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An unspecified ActiveX control in SiteKiosk before 6.5.150 is installed "safe for scripting", which allows local users to bypass security protections and read arbitrary files via certain functions.

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

It affects 1 product.


Products: Sitekiosk Sitekiosk.

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

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

## Is CVE-2006-6510 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-6509](https://insights.sbomify.com/CVE-2006-6509/): Cross-site scripting in n/a (medium 4.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6510 is a low-severity vulnerability in n/a, published on 14 Dec 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-6510 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-6510/ (Markdown: https://insights.sbomify.com/CVE-2006-6510/index.md)
```

## Sources

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

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