# CVE-2026-115806: The Prime Mover – Backup and Migration plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 2.2.


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-g589-p4qg-x28q

## What is CVE-2026-115806?

CVE-2026-115806 is a critical vulnerability in codexonics Prime Mover – Backup and Migration, published on 24 Oct 2026. 

### Official description

The Prime Mover – Backup and Migration plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 2.2.1 via deserialization of untrusted input in the migration search-and-replace routine (recursiveUnserializeReplace()). An unauthenticated attacker can store a crafted, base64-encoded serialized object in wp_comments.comment_content through the standard comment-submission endpoint (wp-comments-post.php). When an administrator subsequently performs a routine Prime Mover export or restore, the plugin base64-decodes that stored value and passes it to unserialize() with no allowed_classes restriction. A Property-Oriented Programming (POP) chain is present in the plugin's own bundled Freemius library (FS_Clone_Manager::__set → FS_Option_Manager::set_option → store() → update_option()), so no additional plugin or theme is required — the plugin ships the gadget itself.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-115806?


## How do I fix CVE-2026-115806?

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

## Is CVE-2026-115806 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115806 and fix it if it is affected.

What it is: CVE-2026-115806 is a critical vulnerability in codexonics Prime Mover – Backup and Migration, published on 24 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115806 in the wild and no public exploit code.

Affected product: codexonics Prime Mover – Backup and Migration. 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-2026-115806/ (Markdown: https://insights.sbomify.com/CVE-2026-115806/index.md)
```

## Sources

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

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