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

> Remote attackers can inject arbitrary web script or HTML into the topic administration page of the RT ticketing system, potentially compromising user sessions.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 Aug 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-2769, GHSA-6gr3-vr3v-86j3

## What is CVE-2012-2769?

CVE-2012-2769 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 Aug 2012. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in the topic administration page in the Extension::MobileUI extension before 1.02 for Best Practical Solutions RT 3.8.x and in Best Practical Solutions RT before 4.0.6 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors.

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

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

It affects 1 product.


Products: Jesse Vincent Extension\.

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

Upgrade to a fixed version.

## Is CVE-2012-2769 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2012-2769 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 Aug 2012. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-2769 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-2769/ (Markdown: https://insights.sbomify.com/CVE-2012-2769/index.md)
```

## Sources

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

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