Prime Mover – Backup and Migration <= 2.2.1 - Unauthenticated PHP Object Injection via Stored Content Processed During Migration Search-Replace
- ID
- WPSEC-2026-1305
- Plugin
- Prime Mover – Backup and Migration (prime-mover)
- Affected
- all versions before 2.2.2
- Remediation
- Update to 2.2.2 or later.
- CVSS 3.1
- CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
- Weakness
- CWE-502
- Usage
- Plugin Low · Affected versions Low among sites WPSec scans, 2026-10-21
- Attack surface
- Prime Mover – Backup and Migration on WPSec AttackSurface
- Fix released
- Published
Description
The Prime Mover – Backup and Migration plugin for WordPress is vulnerable to PHP Object Injection via the database search-and-replace step of a migration or restore in all versions up to, and including, 2.2.1. This is due to deserialization of untrusted input: every database value that contains a search string (such as the old site URL) is passed to unserialize() with no class restriction, and the result is unserialized again if it is itself a string. This makes it possible for unauthenticated attackers to plant a serialized PHP object in stored content, such as a comment. The object is instantiated when an administrator later migrates or restores the site. No known POP chain is present in the vulnerable software itself. If a POP chain is present through another plugin or theme on the target system, it could let the attacker delete arbitrary files, retrieve sensitive data, or execute code.
References
- https://wpsec.com/vuln/WPSEC-2026-1305/
- https://plugins.svn.wordpress.org/prime-mover/tags/2.2.2/
- https://wordpress.org/plugins/prime-mover/
Published by WPSec. Provided as is, without warranty. Corrections: contact us.
This advisory as JSON or Markdown · All advisories: JSON, RSS