# CVE-2022-3417: WPtouch < 4.3.45 - Admin+ PHP Object Injection

> An admin user can trigger PHP object injection via a malicious settings file, potentially leading to code execution on the WordPress site.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Jan 2023
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-6rpp-h47m-wx9v

## What is CVE-2022-3417?

CVE-2022-3417 is a high-severity unsafe deserialization vulnerability in Unknown WPtouch, published on 9 Jan 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The WPtouch WordPress plugin before 4.3.45 unserialises the content of an imported settings file, which could lead to PHP object injections issues when an user import (intentionally or not) a malicious settings file and a suitable gadget chain is present on the blog.

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

It affects 1 product.


Products: Bravenewcode Wptouch.

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

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

## Is CVE-2022-3417 being exploited?

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

## Other vulnerabilities in Unknown WPtouch

- [CVE-2011-4803](https://insights.sbomify.com/CVE-2011-4803/): SQL injection in n/a (high 7.5)
- [CVE-2022-3416](https://insights.sbomify.com/CVE-2022-3416/): WPtouch < 4.3.45 - Admin+ Arbitrary File Upload (high 7.2)
- [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-3417 and fix it if it is affected.

What it is: CVE-2022-3417 is a high-severity unsafe deserialization vulnerability in Unknown WPtouch, published on 9 Jan 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-3417 in the wild and no public exploit code.

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-3417/ (Markdown: https://insights.sbomify.com/CVE-2022-3417/index.md)
```

## Sources

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

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