CVE-2026-109555: WP STAGING <= 4.17.0 and WP STAGING Pro <= 6.17.0 - Authenticated (Subscriber+) PHP Object Injection to Remote Code Execution via Database Restore and Staging Reset
The WP STAGING and WP STAGING Pro plugins for WordPress are vulnerable to PHP Object Injection in all versions up to, and including, 4.17.0 and 6.17.0, respectively, via deserialization of untrusted input during database restore and staging reset. This is due to the database importer treating attacker-controlled text beginning with {WPSTGBINARY} as trusted internal binary data and decoding its hexadecimal suffix into serialized bytes. This makes it possible for authenticated attackers, with Subscriber-level access and above, to plant a malicious serialized object in their own profile. When an Administrator later performs an ordinary database-including restore or staging reset containing that value, and the restored profile metadata is loaded, either during the restore or in a later request, a built-in POP chain can be used to execute arbitrary code on the server. Additional built-in gadget chains allow arbitrary local file read in both WP STAGING and WP STAGING Pro and arbitrary file deletion in WP STAGING Pro. The attacker does not require Administrator credentials or a copy of a backup, but exploitation does require the later privileged restore or reset.
Affected Software
Event History
Frequently Asked Questions
Which users could initiate an attack?
Any authenticated user with Subscriber-level access or higher can plant the malicious serialized object in their own profile. Administrator credentials are not required for the attacker.
What action is required before the payload can execute?
An Administrator must later perform a database-including restore or staging reset that contains the attacker-controlled profile value. The restored profile metadata must then be loaded, either during that operation or in a subsequent request.
Does an attacker need access to a backup file to exploit this issue?
No. The attacker does not need a copy of a backup; they only need authenticated Subscriber-level or greater access and a later privileged restore or reset.
Are the possible impacts different between the free and Pro editions?
Both editions have built-in gadget chains that can enable arbitrary code execution and arbitrary local file reads. WP STAGING Pro also has a built-in gadget chain that can enable arbitrary file deletion.
Which plugin versions are affected?
WP STAGING versions through 4.17.0 and WP STAGING Pro versions through 6.17.0 are affected.