# CVE-2015-3295: Cross-site scripting in n/a

> Attackers can inject malicious scripts via data URLs in markdown-it, leading to cross-site scripting attacks.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jun 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-3295, GHSA-qfv2-8p99-wj5c

## What is CVE-2015-3295?

CVE-2015-3295 is a medium-severity cross-site scripting vulnerability in n/a, published on 7 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

markdown-it before 4.1.0 does not block data: URLs.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2015-3295?

It affects 1 product.


Products: Markdown-It Project Markdown-It.

## How do I fix CVE-2015-3295?

Upgrade to a fixed version.

## Is CVE-2015-3295 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-2327](https://insights.sbomify.com/CVE-2026-2327/): markdown-it is has a Regular Expression Denial of Service (ReDoS) (medium 6.9)
- [CVE-2025-7969](https://insights.sbomify.com/CVE-2025-7969/): Markdown-it 14.1.0 - Cross-site scripting (XSS) (medium 6.9)
- [CVE-2026-48988](https://insights.sbomify.com/CVE-2026-48988/): markdown-it: Quadratic complexity DoS in smartquotes rule via replaceAt string operations (medium 5.3)
- [CVE-2022-21670](https://insights.sbomify.com/CVE-2022-21670/): Uncontrolled Resource Consumption in markdown-it (medium 5.3)
- [CVE-2015-10005](https://insights.sbomify.com/CVE-2015-10005/): markdown-it html_re.js redos (low 3.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-3295 and fix it if it is affected.

What it is: CVE-2015-3295 is a medium-severity cross-site scripting vulnerability in n/a, published on 7 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-3295 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-2015-3295/ (Markdown: https://insights.sbomify.com/CVE-2015-3295/index.md)
```

## Sources

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

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