# CVE-2013-5964: Cross-site scripting in n/a

> Authenticated administrators can inject arbitrary scripts via flag titles in the Drupal Flag module, potentially compromising admin sessions.

- **Severity:** Low 2.1 (`AV:N/AC:H/Au:S/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:** 30 Sep 2013
- **Updated:** 17 Sep 2024
- **Also known as:** CVE-2013-4336, GHSA-7hf9-xmq4-prrq

## What is CVE-2013-5964?

CVE-2013-5964 is a low-severity cross-site scripting vulnerability in n/a, published on 30 Sep 2013. 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 administration page in the Flag module 7.x-3.x before 7.x-3.1 for Drupal allows remote authenticated users with the "Administer flags" permission to inject arbitrary web script or HTML via the flag title.

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

## Which versions are affected by CVE-2013-5964?

It affects 1 product.


Products: Joachim Noreiko Flag Module.

## How do I fix CVE-2013-5964?

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

## Is CVE-2013-5964 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-5964 and fix it if it is affected.

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

## Sources

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

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