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

> Remote attackers can inject arbitrary web script via content titles in breadcrumbs when a specific module setting is enabled.

- **Severity:** Low 2.6 (`AV:N/AC:H/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:** 27 Jun 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-784q-3wpw-gfhc

## What is CVE-2012-2710?

CVE-2012-2710 is a low-severity cross-site scripting vulnerability in n/a, published on 27 Jun 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

Cross-site scripting (XSS) vulnerability in the Zen module 6.x-1.x before 6.x-1.1 for Drupal, when "Append the content title to the end of the breadcrumb" is enabled, allows remote attackers to inject arbitrary web script or HTML via the content title in a breadcrumb.

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

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

It affects 1 product.


Products: John Albin Zen.

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

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

## Is CVE-2012-2710 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2012-2710 is a low-severity cross-site scripting vulnerability in n/a, published on 27 Jun 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-2710 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-2710/ (Markdown: https://insights.sbomify.com/CVE-2012-2710/index.md)
```

## Sources

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

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