# CVE-2017-15287: Cross-site scripting in n/a

> Cross-site scripting in Dreambox BouquetEditor allows attackers to inject scripts via bouquet names or file parameters, potentially compromising the device interface.

- **Severity:** Medium 6.1 (`CVSS:3.0/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:** No
- **Published:** 12 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xww9-gc2f-7jf6

## What is CVE-2017-15287?

CVE-2017-15287 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 Oct 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

There is XSS in the BouquetEditor WebPlugin for Dream Multimedia Dreambox devices, as demonstrated by the "Name des Bouquets" field, or the file parameter to the /file URI.

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

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

It affects 1 product.


Products: Bouqueteditor Project Bouqueteditor.

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

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

## Is CVE-2017-15287 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-15287 exists.

Public exploit code:

- Dreambox Plugin BouquetEditor - Cross-Site Scripting (exploitdb)
- Dreambox WebControl 2.0.0 - Cross-Site Scripting (nuclei): http/cves/2017/CVE-2017-15287.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15287 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 Oct 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-15287 exists.

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

## Sources

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

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