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

> Remote attackers can inject arbitrary web script or HTML into Cumin via widgets or pages, 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:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Apr 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-v47v-hq34-79pq, RHSA-2012:0476, RHSA-2012:0477

## What is CVE-2012-1575?

CVE-2012-1575 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Apr 2012. It can be exploited over the network, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in Cumin before r5238 allow remote attackers to inject arbitrary web script or HTML via vectors involving (1) widgets or (2) pages.

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

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cumin` | Red Hat:enterprise_mrg:2::el5 | All versions | 0:0.1.5192-4.el5 |
| `cumin` | Red Hat:enterprise_mrg:2:server:el6 | All versions | 0:0.1.5192-5.el6 |

Products: Trevor Mckay Cumin.

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

Upgrade to a fixed version.

## Is CVE-2012-1575 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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