WP Security CheckVulnerability data as of November 22, 2026

Vulnerability alerts / November 19, 2026

Vulnerability in WP STAGING – WordPress Backups, Restore, Migration & Clone — CVE-2026-109555

HighSeverity
CVSS 8
0.4%Estimated exploit probability
EPSS
100,000+ sitesInstalls
4.18.0Fixed in

What to do now

Update WP STAGING – WordPress Backups, Restore, Migration & Clone to 4.18.0 or later.

Affected versions

  • Everything up to and including 4.17.0
  • Everything up to and including 6.17.0

Affected: WP STAGING – WordPress Backups, Restore, Migration & Clone (plugin, wp-staging)

Check: The plugin on wordpress.org / Our record for WP STAGING – WordPress Backups, Restore, Migration & Clone

What the vulnerability is

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 {WPSTG_BINARY} 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.

This description is reproduced verbatim from the public vulnerability record.

Sources

See other alerts