# CVE-2017-15685: XML Injection in Crafter CMS Crafter Studio 3.0.1

> An unauthenticated attacker can exploit an XML External Entity vulnerability in Crafter Studio to retrieve operating system files out-of-band.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Nov 2020
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-5hr6-vc97-qxxh

## What is CVE-2017-15685?

CVE-2017-15685 is a high-severity vulnerability in n/a, published on 27 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Crafter CMS Crafter Studio 3.0.1 is affected by: XML External Entity (XXE). An unauthenticated attacker is able to create a site with specially crafted XML that allows the retrieval of OS files out-of-band.

Weakness: CWE-91 (XML Injection)

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

2 open source packages ship an affected version, including org.craftercms:crafter-studio. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.craftercms:crafter-studio` | Maven | All versions | 3.0.2 |
| `org.craftercms:crafter-studio` | Maven | All versions | 3.0.2 |

Products: Craftercms Crafter Cms.

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

Upgrade org.craftercms:crafter-studio to 3.0.2 or later.

## Is CVE-2017-15685 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-15681](https://insights.sbomify.com/CVE-2017-15681/): Path Traversal in Crafter CMS Crafter Studio (critical 9.8)
- [CVE-2018-19907](https://insights.sbomify.com/CVE-2018-19907/): OS Command Injection in craftercms:crafter-studio (high 8.8)
- [CVE-2017-15683](https://insights.sbomify.com/CVE-2017-15683/): XML injection in Crafter CMS (high 8.6)
- [CVE-2021-23264](https://insights.sbomify.com/CVE-2021-23264/): Exposure of Resource to Wrong Sphere in org.craftercms:crafter-search (high 8.1)
- [CVE-2021-23267](https://insights.sbomify.com/CVE-2021-23267/): Improper Control of Dynamically-Managed Code Resources in Crafter Studio (high 7.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15685 is a high-severity vulnerability in n/a, published on 27 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-15685 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.craftercms:crafter-studio (Maven): affected all versions; fixed in 3.0.2
- org.craftercms:crafter-studio (Maven): affected all versions; fixed in 3.0.2

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

## Sources

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

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