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

> A privileged user can upload a malicious PHP template file to execute arbitrary code on the OCS Inventory Server.

- **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:** Yes
- **Published:** 6 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-14857, GHSA-3g3v-97v3-vj6w

## What is CVE-2018-14857?

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

### Official description

Unrestricted file upload (with remote code execution) in require/mail/NotificationMail.php in Webconsole in OCS Inventory NG OCS Inventory Server through 2.5 allows a privileged user to gain access to the server via a template file containing PHP code, because file extensions other than .html are permitted.

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

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

It affects 1 product.


Products: Ocsinventory-Ng Ocs Inventory Server.

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

Apply the vendor's patch.

## Is CVE-2018-14857 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-22675](https://insights.sbomify.com/CVE-2026-22675/): OCS Inventory NG Server Stored XSS via User-Agent (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-14857 is a high-severity vulnerability in n/a, published on 6 Aug 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-14857 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-14857/ (Markdown: https://insights.sbomify.com/CVE-2018-14857/index.md)
```

## Sources

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

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