# CVE-2017-11439: In Sitecore 8.2, there is reflected XSS in the shell/Applications/Tools/Run Program parameter.


- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5q5c-m5v5-9c5f

## What is CVE-2017-11439?

CVE-2017-11439 is a medium-severity vulnerability in n/a, published on 19 Jul 2017. 

### Official description

In Sitecore 8.2, there is reflected XSS in the shell/Applications/Tools/Run Program parameter.

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

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

It affects 1 product.


Products: Sitecore Cms.

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

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

## Is CVE-2017-11439 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-9874](https://insights.sbomify.com/CVE-2019-9874/): Sitecore CMS and Experience Platform (XP) Deserialization (critical 9.8, exploited in the wild)
- [CVE-2019-9875](https://insights.sbomify.com/CVE-2019-9875/): Sitecore CMS and Experience Platform (XP) Deserialization (high 8.8, exploited in the wild)
- [CVE-2019-11198](https://insights.sbomify.com/CVE-2019-11198/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2017-11440](https://insights.sbomify.com/CVE-2017-11440/): In Sitecore 8.2, there is absolute path traversal via the shell/Applications/Layouts/IDE.aspx fi parameter and the admin/LinqScratchPad.aspx Reference parameter. (medium 4.9)
- [CVE-2014-100004](https://insights.sbomify.com/CVE-2014-100004/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-11439 is a medium-severity vulnerability in n/a, published on 19 Jul 2017. 
Exploitation: There is no known exploitation of CVE-2017-11439 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-2017-11439/ (Markdown: https://insights.sbomify.com/CVE-2017-11439/index.md)
```

## Sources

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

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