# CVE-2024-10962: Migration, Backup, Staging – WPvivid <= 0.9.107 - Unauthenticated PHP Object Injection

> Unauthenticated attackers can inject PHP objects via deserialization, potentially leading to code execution or data theft if a POP chain exists.

- **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:** 14 Nov 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-q5hh-p536-9725

## What is CVE-2024-10962?

CVE-2024-10962 is a high-severity unsafe deserialization vulnerability in wpvividplugins WPvivid — Backup, Migration & Staging, published on 14 Nov 2024. 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 Migration, Backup, Staging – WPvivid plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 0.9.107 via deserialization of untrusted input in the 'replace_row_data' and 'replace_serialize_data' functions. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code. An administrator must create a staging site to trigger the exploit.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2024-10962?

It affects 1 product.


Products: Wpvivid Migration\, Backup\, Staging.

## How do I fix CVE-2024-10962?

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

## Is CVE-2024-10962 being exploited?

There is no known exploitation of CVE-2024-10962 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-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)
- [CVE-2023-5576](https://insights.sbomify.com/CVE-2023-5576/): Migration, Backup, Staging – WPvivid <= 0.9.91 - Google Drive Client Secret Exposure (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-10962 and fix it if it is affected.

What it is: CVE-2024-10962 is a high-severity unsafe deserialization vulnerability in wpvividplugins WPvivid — Backup, Migration & Staging, published on 14 Nov 2024. 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-2024-10962 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-2024-10962/ (Markdown: https://insights.sbomify.com/CVE-2024-10962/index.md)
```

## Sources

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

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