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

> Attackers can inject malicious HTML into video comments, potentially executing scripts in victim browsers.

- **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:** 18 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r72h-qv83-vm45

## What is CVE-2017-17649?

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

Readymade Video Sharing Script 3.2 has HTML Injection via the single-video-detail.php comment parameter.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Readymade Video Sharing Script Project Readymade Video Sharing Script.

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

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

## Is CVE-2017-17649 being exploited?

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

Public exploit code:

- Readymade Video Sharing Script 3.2 - HTML Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-17892](https://insights.sbomify.com/CVE-2017-17892/): SQL injection in n/a (critical 9.8)
- [CVE-2017-17627](https://insights.sbomify.com/CVE-2017-17627/): SQL injection in n/a (critical 9.8)
- [CVE-2017-17891](https://insights.sbomify.com/CVE-2017-17891/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2017-17893](https://insights.sbomify.com/CVE-2017-17893/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17649 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 Dec 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-17649 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-17649/ (Markdown: https://insights.sbomify.com/CVE-2017-17649/index.md)
```

## Sources

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

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