# CVE-2011-5297: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML into TTChat via msg or username parameters, requiring user interaction to execute.

- **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:** 1 Jan 2015
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-2x3g-5wc5-pwch

## What is CVE-2011-5297?

CVE-2011-5297 is a medium-severity cross-site scripting vulnerability in n/a, published on 1 Jan 2015. 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

Multiple cross-site scripting (XSS) vulnerabilities in TTChat 1.0.4 allow remote attackers to inject arbitrary web script or HTML via (1) the msg parameter to default.php or (2) the username parameter to chat_form.php.

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

## Which versions are affected by CVE-2011-5297?

It affects 1 product.


Products: Ttfreeware Tigertoms Chat Room.

## How do I fix CVE-2011-5297?

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

## Is CVE-2011-5297 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-5297 and fix it if it is affected.

What it is: CVE-2011-5297 is a medium-severity cross-site scripting vulnerability in n/a, published on 1 Jan 2015. 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-2011-5297 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-2011-5297/ (Markdown: https://insights.sbomify.com/CVE-2011-5297/index.md)
```

## Sources

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

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