# CVE-2019-14794: File upload in n/a

> The Meta Box plugin for WordPress mishandles file uploads to custom folders, potentially allowing attackers to upload malicious files and execute code.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h8gw-46gf-w8c5

## What is CVE-2019-14794?

CVE-2019-14794 is a high-severity vulnerability in n/a, published on 9 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Meta Box plugin before 4.16.2 for WordPress mishandles the uploading of files to custom folders.

Weakness: CWE-19

## Which versions are affected by CVE-2019-14794?

It affects 1 product.


Products: Metabox Meta Box.

## How do I fix CVE-2019-14794?

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

## Is CVE-2019-14794 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-14793](https://insights.sbomify.com/CVE-2019-14793/): Missing authorization in n/a (medium 6.5)
- [CVE-2023-6526](https://insights.sbomify.com/CVE-2023-6526/): Meta Box – WordPress Custom Fields Framework <= 5.9.2 - Authenticated (Contributor+) Stored Cross-Site Scripting (medium 6.4)
- [CVE-2024-1204](https://insights.sbomify.com/CVE-2024-1204/): Meta Box < 5.9.4 - Contributor+ Arbitrary Posts' Custom Field Disclosure (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-14794 and fix it if it is affected.

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

## Sources

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

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