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

> Attackers can upload malicious PHP files via the formmailer widget to execute arbitrary code on websites built with Zeta Producer Desktop CMS.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2rmf-9mpq-4vh6

## What is CVE-2018-13981?

CVE-2018-13981 is a critical vulnerability in n/a, published on 16 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The websites that were built from Zeta Producer Desktop CMS before 14.2.1 are vulnerable to unauthenticated remote code execution due to a default component that permits arbitrary upload of PHP files, because the formmailer widget blocks .php files but not .php5 or .phtml files. This is related to /assets/php/formmailer/SendEmail.php and /assets/php/formmailer/functions.php.

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

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

It affects 1 product.


Products: Zeta-Producer Zeta Producer Desktop Cms.

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

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

## Is CVE-2018-13981 being exploited?

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

Public exploit code:

- Zeta Producer Desktop CMS 14.2.0 - Remote Code Execution / Local File Disclosure (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-13981 is a critical vulnerability in n/a, published on 16 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-13981 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-13981/ (Markdown: https://insights.sbomify.com/CVE-2018-13981/index.md)
```

## Sources

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

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