# CVE-2017-6104: File upload in Wordpress Plugin Mobile App Native 3.0

> Attackers can upload malicious files to the Mobile App Native WordPress plugin, potentially leading to remote code execution.

- **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:** 2 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9pfx-9vhr-v8mj

## What is CVE-2017-6104?

CVE-2017-6104 is a high-severity vulnerability in zendkmobileapp Wordpress Plugin Mobile App Native 3.0, published on 2 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Remote file upload vulnerability in Wordpress Plugin Mobile App Native 3.0.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2017-6104?

It affects 1 product.


Products: Zen Mobile App Native Project Zen Mobile App Native.

## How do I fix CVE-2017-6104?

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

## Is CVE-2017-6104 being exploited?

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

Public exploit code:

- Multiple WordPress Plugins - Arbitrary File Upload (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6104 and fix it if it is affected.

What it is: CVE-2017-6104 is a high-severity vulnerability in zendkmobileapp Wordpress Plugin Mobile App Native 3.0, published on 2 Mar 2017. 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-2017-6104 in the wild and no public exploit code.

Affected product: zendkmobileapp Wordpress Plugin Mobile App Native 3.0. 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-2017-6104/ (Markdown: https://insights.sbomify.com/CVE-2017-6104/index.md)
```

## Sources

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

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