# CVE-2017-9516: Craft CMS XSS Vulnerability

> Attackers can execute arbitrary scripts in user browsers by uploading malicious SVG files to Craft CMS.

- **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
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6pvw-hh48-jx7p

## What is CVE-2017-9516?

CVE-2017-9516 is a medium-severity cross-site scripting vulnerability in Craftcms Craft Cms, published on 8 Jun 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Craft CMS before 2.6.2982 allows for a potential XSS attack vector by uploading a malicious SVG file.

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `craftcms/cms` | Packagist | All versions | 2.6.2982 |
| `craftcms/cms` | Packagist | All versions | 2.6.2982 |

Products: Craftcms Craft Cms.

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

Upgrade craftcms/cms to 2.6.2982 or later.

## Is CVE-2017-9516 being exploited?

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

Public exploit code:

- Craft CMS 2.6 - Cross-Site Scripting (exploitdb)

## Other vulnerabilities in Craftcms Craft Cms

- [CVE-2025-32432](https://insights.sbomify.com/CVE-2025-32432/): Craft CMS Code Injection (critical 10.0, exploited in the wild)
- [CVE-2024-56145](https://insights.sbomify.com/CVE-2024-56145/): Craft CMS Code Injection (critical 9.3, exploited in the wild)
- [CVE-2025-23209](https://insights.sbomify.com/CVE-2025-23209/): Craft CMS Code Injection (high 8.1, exploited in the wild)
- [CVE-2025-35939](https://insights.sbomify.com/CVE-2025-35939/): Craft CMS External Control of Assumed-Immutable Web Parameter (medium 6.9, exploited in the wild)
- [CVE-2023-41892](https://insights.sbomify.com/CVE-2023-41892/): Craft CMS Remote Code Execution vulnerability (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9516 is a medium-severity cross-site scripting vulnerability in Craftcms Craft Cms, published on 8 Jun 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-9516 in the wild and no public exploit code.

Affected packages and fixed versions:
- craftcms/cms (Packagist): affected all versions; fixed in 2.6.2982
- craftcms/cms (Packagist): affected all versions; fixed in 2.6.2982

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

## Sources

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

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