# CVE-2018-25162: 2-Plan Team 1.0.4 Arbitrary File Upload via managefile.php

> Authenticated attackers can upload executable PHP files to achieve remote code execution on the 2-Plan Team web application.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 6 Mar 2026
- **Updated:** 9 Mar 2026
- **Also known as:** GHSA-mr8v-9m78-w527

## What is CVE-2018-25162?

CVE-2018-25162 is a high-severity vulnerability in 2-Plan Plan Team, published on 6 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

2-Plan Team 1.0.4 contains an arbitrary file upload vulnerability that allows authenticated attackers to upload executable PHP files by sending multipart form data to managefile.php. Attackers can upload PHP files through the userfile1 parameter with action=upload, which are stored in the files directory and executed by the web server for remote code execution.

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

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


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

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

## Is CVE-2018-25162 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25162 is a high-severity vulnerability in 2-Plan Plan Team, published on 6 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25162 exists.

Affected product: 2-Plan Plan Team. 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-25162/ (Markdown: https://insights.sbomify.com/CVE-2018-25162/index.md)
```

## Sources

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

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