# CVE-2017-7251: Pi Cross-site Scripting vulnerability

> An attacker can execute arbitrary HTML and script code in a browser via insufficient filtration of user-supplied data in the markdown preview feature.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9v3w-m552-m6ff

## What is CVE-2017-7251?

CVE-2017-7251 is a medium-severity cross-site scripting vulnerability in n/a, published on 23 Mar 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A Cross-Site Scripting (XSS) was discovered in pi-engine/pi 2.5.0. The vulnerability exists due to insufficient filtration of user-supplied data (preview) passed to the "pi-develop/www/script/editor/markitup/preview/markdown.php" URL. An attacker could execute arbitrary HTML and script code in a browser in the context of the vulnerable website.

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

## Which versions are affected by CVE-2017-7251?

2 open source packages ship an affected version, including pi/pi. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pi/pi` | Packagist | All versions | 2.6.0-alpha1 |
| `pi/pi` | Packagist | All versions | 2.6.0-alpha1 |

Products: Piengine Pi.

## How do I fix CVE-2017-7251?

Upgrade pi/pi to 2.6.0-alpha1 or later.

## Is CVE-2017-7251 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-7251 and fix it if it is affected.

What it is: CVE-2017-7251 is a medium-severity cross-site scripting vulnerability in n/a, published on 23 Mar 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-7251 in the wild and no public exploit code.

Affected packages and fixed versions:
- pi/pi (Packagist): affected all versions; fixed in 2.6.0-alpha1
- pi/pi (Packagist): affected all versions; fixed in 2.6.0-alpha1

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

## Sources

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

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