# CVE-2006-0102: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script via javascript scheme in bbcode tags, allowing session hijacking or malicious actions.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vqgf-cgc4-xcmj

## What is CVE-2006-0102?

CVE-2006-0102 is a medium-severity cross-site scripting vulnerability in n/a, published on 6 Jan 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in TinyPHPForum (TPF) 3.6 and earlier allows remote attackers to inject arbitrary web script via a javascript: scheme in an "[a]" bbcode tag, possibly the txt parameter to action.php.

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

It affects 1 product.


Products: Ralph Capper Tinyphpforum.

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

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

## Is CVE-2006-0102 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-0103](https://insights.sbomify.com/CVE-2006-0103/): Information disclosure in n/a (medium 5.0)
- [CVE-2006-0104](https://insights.sbomify.com/CVE-2006-0104/): Path traversal in n/a (medium 5.0)
- [CVE-2006-1898](https://insights.sbomify.com/CVE-2006-1898/): Cross-site scripting in n/a (low 2.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0102 is a medium-severity cross-site scripting vulnerability in n/a, published on 6 Jan 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-0102 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-0102/ (Markdown: https://insights.sbomify.com/CVE-2006-0102/index.md)
```

## Sources

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

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