# CVE-2012-2909: Cross-site scripting in n/a

> Remote attackers can inject arbitrary scripts via multiple input fields in Viscacha, potentially compromising user sessions and data.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 May 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-j7q8-hh4q-9hpf

## What is CVE-2012-2909?

CVE-2012-2909 is a medium-severity cross-site scripting vulnerability in n/a, published on 21 May 2012. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in Viscacha 0.8.1.1 allow remote attackers to inject arbitrary web script or HTML via the (1) text field in the Private Messages System, (2) Bad Word field in Zensur, or (3) Portal or (4) Topic field in Kommentar.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2012-2909?

It affects 1 product.


Products: Viscacha Viscacha.

## How do I fix CVE-2012-2909?

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

## Is CVE-2012-2909 being exploited?

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

Public exploit code:

- Viscacha Forum CMS 0.8.1.1 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-2908](https://insights.sbomify.com/CVE-2012-2908/): SQL injection in n/a (high 7.5)
- [CVE-2009-4567](https://insights.sbomify.com/CVE-2009-4567/): Cross-site scripting in n/a (low 3.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2909 and fix it if it is affected.

What it is: CVE-2012-2909 is a medium-severity cross-site scripting vulnerability in n/a, published on 21 May 2012. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-2909 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-2012-2909/ (Markdown: https://insights.sbomify.com/CVE-2012-2909/index.md)
```

## Sources

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

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