# CVE-2022-2442: Migration, Backup, Staging – WPvivid <= 0.9.74 - Authenticated (Admin+) PHAR Deserialization

> Authenticated administrators can achieve arbitrary code execution via PHAR deserialization in the WPvivid 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:** 6 Sep 2022
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-x57g-xj73-77gw

## What is CVE-2022-2442?

CVE-2022-2442 is a high-severity unsafe deserialization vulnerability in wpvividplugins WPvivid — Backup, Migration & Staging, published on 6 Sep 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Migration, Backup, Staging – WPvivid plugin for WordPress is vulnerable to deserialization of untrusted input via the   'path' parameter in versions up to, and including 0.9.74. This makes it possible for authenticated attackers with administrative privileges to call files using a PHAR wrapper that will deserialize and call arbitrary PHP Objects that can be used to perform a variety of malicious actions granted a POP chain is also present. It also requires that the attacker is successful in uploading a file with the serialized payload.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Wpvivid Migration\, Backup\, Staging.

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

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

## Is CVE-2022-2442 being exploited?

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

## Other vulnerabilities in wpvividplugins WPvivid — Backup, Migration & Staging

- [CVE-2024-1981](https://insights.sbomify.com/CVE-2024-1981/): SQL injection in Migration, Backup, Staging – WPvivid (critical 9.8)
- [CVE-2024-10962](https://insights.sbomify.com/CVE-2024-10962/): Migration, Backup, Staging – WPvivid <= 0.9.107 - Unauthenticated PHP Object Injection (high 8.8)
- [CVE-2020-36842](https://insights.sbomify.com/CVE-2020-36842/): Migration, Backup, Staging – WPvivid <= 0.9.35 - Authenticated (Subscriber+) Arbitrary File Upload (high 8.8)
- [CVE-2023-41243](https://insights.sbomify.com/CVE-2023-41243/): WordPress WPvivid Backup Plugin plugin <= 0.9.90 - Privilege Escalation on Staging Environment vulnerability (high 8.8)
- [CVE-2023-4274](https://insights.sbomify.com/CVE-2023-4274/): Path traversal in Migration, Backup, Staging – WPvivid (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-2442 is a high-severity unsafe deserialization vulnerability in wpvividplugins WPvivid — Backup, Migration & Staging, published on 6 Sep 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-2442 in the wild and no public exploit code.

Affected product: wpvividplugins WPvivid — Backup, Migration & Staging. 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-2442/ (Markdown: https://insights.sbomify.com/CVE-2022-2442/index.md)
```

## Sources

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

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