Answer in brief
CVE-2026-109555 records a High severity (CVSS 8.0) vulnerability in 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 current sources do not mark it as known exploited. The current feed maps renehermi/WP STAGING – Backups & Restore, Migration & Clone Plugin – Cloud Backups, Scheduled Backups (generic), WPStaging/WP STAGING Pro WordPress Backup Plugin (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps renehermi/WP STAGING – Backups & Restore, Migration & Clone Plugin – Cloud Backups, Scheduled Backups (generic), WPStaging/WP STAGING Pro WordPress Backup Plugin (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| renehermi/WP STAGING – Backups & Restore, Migration & Clone Plugin – Cloud Backups, Scheduled Backupsgeneric | >=0 <=4.17.0 | Not reported |
| WPStaging/WP STAGING Pro WordPress Backup Plugingeneric | >=0 <=6.17.0 | Not reported |
Published upstream
Nov 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 19, 2026
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.
Quoted source text, attributed separately from HOL analysis.