# CVE-2020-25042: File upload in n/a

> Authenticated administrators can upload arbitrary PHP files to execute code on the server.

- **Severity:** High 7.2 (`CVSS:3.1/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:** 3 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8h22-fc39-v23w

## What is CVE-2020-25042?

CVE-2020-25042 is a high-severity vulnerability in n/a, published on 3 Sep 2020. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An arbitrary file upload issue exists in Mara CMS 7.5. In order to exploit this, an attacker must have a valid authenticated (admin/manager) session and make a codebase/dir.php?type=filenew request to upload PHP code to codebase/handler.php.

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

## Which versions are affected by CVE-2020-25042?

It affects 1 product.


Products: Maracms Maracms.

## How do I fix CVE-2020-25042?

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

## Is CVE-2020-25042 being exploited?

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

Public exploit code:

- PoC for CVE-2020-25042: automated Mara CMS 7.5 authenticated PHP upload to RCE, with login hash handling, shell reuse, custom payload support, and clean CLI output. (github_poc): https://github.com/Groppoxx/CVE-2020-25042-PoC
- MaraCMS Arbitrary PHP File Upload (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-25042 and fix it if it is affected.

What it is: CVE-2020-25042 is a high-severity vulnerability in n/a, published on 3 Sep 2020. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-25042 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-2020-25042/ (Markdown: https://insights.sbomify.com/CVE-2020-25042/index.md)
```

## Sources

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

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