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

> Remote attackers can inject arbitrary JavaScript into WikkaWiki via forced links, potentially executing code in victim browsers.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** 24 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vr4j-7q89-99qc

## What is CVE-2006-7050?

CVE-2006-7050 is a medium-severity cross-site scripting vulnerability in n/a, published on 24 Feb 2007. 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 WikkaWiki (Wikka Wiki) before 1.1.6.2 allows remote attackers to inject arbitrary javascript via (1) events in forced links (url parameter) that are not properly handled in formatters/wakka.php, and possibly (2) other vectors in wikka.php.

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

It affects 1 product.


Products: Wikkawiki Wikkawiki.

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

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

## Is CVE-2006-7050 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-2613](https://insights.sbomify.com/CVE-2007-2613/): Code injection in n/a (high 8.3)
- [CVE-2011-4448](https://insights.sbomify.com/CVE-2011-4448/): SQL injection in n/a (high 7.5)
- [CVE-2007-2612](https://insights.sbomify.com/CVE-2007-2612/): SQL injection in n/a (high 7.5)
- [CVE-2006-7049](https://insights.sbomify.com/CVE-2006-7049/): Path traversal in n/a (high 7.5)
- [CVE-2011-4449](https://insights.sbomify.com/CVE-2011-4449/): File upload in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-7050 is a medium-severity cross-site scripting vulnerability in n/a, published on 24 Feb 2007. 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-7050 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-7050/ (Markdown: https://insights.sbomify.com/CVE-2006-7050/index.md)
```

## Sources

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

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