# CVE-2022-3416: WPtouch < 4.3.45 - Admin+ Arbitrary File Upload

> High-privilege users can upload arbitrary files to the server due to improper image validation in the WPtouch WordPress plugin.

- **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:** 9 Jan 2023
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-m7v9-fq6q-w2wp

## What is CVE-2022-3416?

CVE-2022-3416 is a high-severity vulnerability in Unknown WPtouch, published on 9 Jan 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The WPtouch WordPress plugin before 4.3.45 does not properly validate images to be uploaded, allowing high privilege users such as admin to upload arbitrary files on the server even when they should not be allowed to (for example in multisite setup)

## Which versions are affected by CVE-2022-3416?

It affects 1 product.


Products: Bravenewcode Wptouch.

## How do I fix CVE-2022-3416?

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

## Is CVE-2022-3416 being exploited?

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

## Other vulnerabilities in Unknown WPtouch

- [CVE-2022-3417](https://insights.sbomify.com/CVE-2022-3417/): WPtouch < 4.3.45 - Admin+ PHP Object Injection (high 8.8)
- [CVE-2011-4803](https://insights.sbomify.com/CVE-2011-4803/): SQL injection in n/a (high 7.5)
- [CVE-2010-4779](https://insights.sbomify.com/CVE-2010-4779/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3416 and fix it if it is affected.

What it is: CVE-2022-3416 is a high-severity vulnerability in Unknown WPtouch, published on 9 Jan 2023. 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-2022-3416 exists.

Affected product: Unknown WPtouch. 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-2022-3416/ (Markdown: https://insights.sbomify.com/CVE-2022-3416/index.md)
```

## Sources

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

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