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

Published Nov 19, 2026
·
Updated

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

2 affected components
WP STAGING WP STAGING<=4.17.0
WP STAGING WP STAGING Pro<=6.17.0

Event History

Nov 19, 2026
CVE Published
via MITRE·05:33 AM
Data Sourced
via MITRE·05:33 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:16 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

5

Which plugin versions are affected?

WP STAGING versions through 4.17.0 and WP STAGING Pro versions through 6.17.0 are affected.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203