# CVE-2018-17139: File upload in n/a

> Attackers can upload malicious PHP files to execute arbitrary code remotely on UltimatePOS installations.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9x5j-whx3-gg57

## What is CVE-2018-17139?

CVE-2018-17139 is a high-severity vulnerability in n/a, published on 17 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

UltimatePOS 2.5 allows users to upload arbitrary files, which leads to remote command execution by posting to a /products URI with PHP code in a .php file with the image/jpeg content type.

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

## Which versions are affected by CVE-2018-17139?

It affects 1 product.


Products: Ultimatefosters Ultimatepos.

## How do I fix CVE-2018-17139?

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

## Is CVE-2018-17139 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-60503](https://insights.sbomify.com/CVE-2025-60503/): Cross-site scripting in n/a (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-17139 and fix it if it is affected.

What it is: CVE-2018-17139 is a high-severity vulnerability in n/a, published on 17 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-17139 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-2018-17139/ (Markdown: https://insights.sbomify.com/CVE-2018-17139/index.md)
```

## Sources

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

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