# CVE-2017-15948: File upload in n/a

> Attackers with Limited Admin access can upload malicious files to execute code or trigger XSS via the Asset Title field.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Oct 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7g42-fh7c-62xv

## What is CVE-2017-15948?

CVE-2017-15948 is a medium-severity vulnerability in n/a, published on 28 Oct 2017. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Perch Content Management System 3.0.3 allows unrestricted file upload (with resultant XSS) via the Asset Title field in conjunction with the Select File field. This is exploitable with a Limited Admin account.

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

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

It affects 1 product.


Products: Grabaperch Perch.

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

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

## Is CVE-2017-15948 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-53889](https://insights.sbomify.com/CVE-2023-53889/): Perch CMS 3.2 Remote Code Execution via Unrestricted File Upload (high 8.6)
- [CVE-2025-66686](https://insights.sbomify.com/CVE-2025-66686/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2023-53890](https://insights.sbomify.com/CVE-2023-53890/): Perch CMS 3.2 Stored Cross-Site Scripting via SVG File Upload (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15948 is a medium-severity vulnerability in n/a, published on 28 Oct 2017. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-15948 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-15948/ (Markdown: https://insights.sbomify.com/CVE-2017-15948/index.md)
```

## Sources

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

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