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

> Remote attackers can inject arbitrary web script or HTML via the PATH_INFO in the Tracks web application, 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:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Apr 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9vcf-cf55-hwj8

## What is CVE-2011-1671?

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

### Official description

Cross-site scripting (XSS) vulnerability in app/controllers/todos_controller.rb in Tracks 1.7.2, 2.0RC2, and 2.0devel allows remote attackers to inject arbitrary web script or HTML via the PATH_INFO to todos/tag/.  NOTE: some of these details are obtained from third party information.

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

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

It affects 1 product.


Products: Getontracks Tracks.

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

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

## Is CVE-2011-1671 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-1671 exists.

Public exploit code:

- Tracks 1.7.2 - URI Cross-Site Scripting (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-1671 is a medium-severity cross-site scripting vulnerability in n/a, published on 10 Apr 2011. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-1671 exists.

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-1671/ (Markdown: https://insights.sbomify.com/CVE-2011-1671/index.md)
```

## Sources

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

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