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

> Remote attackers can execute arbitrary code by uploading a malicious file with PHP code in its name via the Phonebook import feature.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jrcp-p4m6-q89q

## What is CVE-2017-9101?

CVE-2017-9101 is a critical vulnerability in n/a, published on 21 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

import.php (aka the Phonebook import feature) in PlaySMS 1.4 allows remote code execution via vectors involving the User-Agent HTTP header and PHP code in the name of a file.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Playsms Playsms.

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

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

## Is CVE-2017-9101 being exploited?

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

Public exploit code:

- Exploit for PlaySMS 1.4 authenticated RCE (github_poc): https://github.com/jasperla/CVE-2017-9101
- PlaySMS 1.4 - 'import.php' Remote Code Execution (exploitdb)
- PlaySMS import.php Authenticated CSV File Upload Code Execution (metasploit)
- PlaySMS - 'import.php' (Authenticated) CSV File Upload Code Execution (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2020-8644](https://insights.sbomify.com/CVE-2020-8644/): PlaySMS Server-Side Template Injection (critical 9.8, exploited in the wild)
- [CVE-2022-47034](https://insights.sbomify.com/CVE-2022-47034/): Auth bypass in n/a (critical 9.8)
- [CVE-2021-40373](https://insights.sbomify.com/CVE-2021-40373/): Code injection in n/a (critical 9.8)
- [CVE-2017-9080](https://insights.sbomify.com/CVE-2017-9080/): File upload in n/a (high 8.8)
- [CVE-2008-5881](https://insights.sbomify.com/CVE-2008-5881/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9101 is a critical vulnerability in n/a, published on 21 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-9101 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-9101/ (Markdown: https://insights.sbomify.com/CVE-2017-9101/index.md)
```

## Sources

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

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