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

> Remote attackers can execute arbitrary PHP code by uploading malicious files due to insufficient file type validation in PivotX.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m9p9-rwr4-hjqp

## What is CVE-2017-14958?

CVE-2017-14958 is a high-severity vulnerability in n/a, published on 1 Oct 2017. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

lib.php in PivotX 2.3.11 does not properly block uploads of dangerous file types by admin users, which allows remote PHP code execution via an upload of a .php file.

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

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

It affects 1 product.


Products: Pivotx Pivotx.

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

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

## Is CVE-2017-14958 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-8402](https://insights.sbomify.com/CVE-2017-8402/): File upload in n/a (high 8.8)
- [CVE-2017-7570](https://insights.sbomify.com/CVE-2017-7570/): File upload in n/a (high 8.8)
- [CVE-2015-5457](https://insights.sbomify.com/CVE-2015-5457/): File upload in n/a (high 7.5)
- [CVE-2014-0342](https://insights.sbomify.com/CVE-2014-0342/): File upload in n/a (high 7.5)
- [CVE-2011-1035](https://insights.sbomify.com/CVE-2011-1035/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-14958 is a high-severity vulnerability in n/a, published on 1 Oct 2017. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-14958 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-14958/ (Markdown: https://insights.sbomify.com/CVE-2017-14958/index.md)
```

## Sources

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

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