Summary
This advisory addresses CVE-2026-109555, a PHP Object Injection vulnerability. It affects the WP STAGING and WP STAGING Pro plugins for WordPress. Patched versions 4.18.0 and 6.18.0 are available. There is no evidence of active exploitation.
Affected and patched versions
WP STAGING – Backups & Restore, Migration & Clone Plugin – Cloud Backups, Scheduled Backups (plugin wp-staging): affected 4.17.0 and earlier; fixed in 4.18.0
WP STAGING Pro WordPress Backup Plugin (plugin wp-staging-pro): affected 6.17.0 and earlier; fixed in 6.18.0
Is my site vulnerable?
To determine if a site uses a vulnerable version of WP STAGING or WP STAGING Pro, check the installed plugin version. Log into the WordPress dashboard, navigate to the "Plugins" section, and locate "WP STAGING – Backups & Restore, Migration & Clone Plugin" or "WP STAGING Pro WordPress Backup Plugin". The version number is displayed next to the plugin name. Compare this number with the affected versions listed in this advisory.
What an attacker actually does
CVE-2026-109555 describes a PHP Object Injection vulnerability present in the WP STAGING and WP STAGING Pro plugins. This vulnerability exists in all versions up to and including 4.17.0 for WP STAGING and 6.17.0 for WP STAGING Pro. The issue stems from the deserialization of untrusted input during database restore and staging reset operations.
The plugin's database importer component is designed to handle internal binary data. It treats any text string beginning with {WPSTG_BINARY} as trusted internal data. Following this prefix, the importer decodes a hexadecimal suffix into serialized bytes. This mechanism allows an authenticated attacker, requiring at least Subscriber-level access, to craft and plant a malicious serialized object within their own user profile data.
The exploitation of this vulnerability requires a subsequent action by an Administrator. When an Administrator performs a routine database-including restore or a staging reset operation that involves the compromised profile data, the malicious serialized object is loaded. During this process, or in a later request that loads the restored profile metadata, a built-in PHP Object Injection (POP) chain is triggered. This chain can then be used to execute arbitrary code on the server. Beyond arbitrary code execution, additional built-in gadget chains enable an attacker to read arbitrary local files in both WP STAGING and WP STAGING Pro. In WP STAGING Pro specifically, these gadget chains also allow for arbitrary file deletion. The attacker does not need Administrator credentials or a copy of a backup file to initiate the attack, but the successful execution of the malicious code depends on a later privileged restore or reset action by an Administrator. The NVD entry for this vulnerability notes a CVSS 3.1 Base Score of 8.0 (HIGH).
How to detect a compromise
Detecting a compromise related to CVE-2026-109555 involves looking for specific indicators of unauthorized activity or changes to the WordPress environment. Since this vulnerability can lead to arbitrary code execution, file reading, and file deletion, the signs of compromise may vary.
Review user accounts for any newly created administrative users or unexpected changes to existing administrator privileges. Examine core WordPress files, plugin files, and theme files for modifications that do not correspond to legitimate updates or changes. Look for new, unfamiliar files, especially in directories like wp-content/uploads, wp-content/plugins, or the root WordPress directory.
Check server access logs and WordPress security logs for unusual activity. This includes unexpected requests to administrative endpoints, attempts to upload files, or unusual login patterns. Look for evidence of file access or modification that does not align with normal operations.
If the site uses a file integrity monitoring system, review its reports for any alerts regarding changes to plugin files, core WordPress files, or configuration files. While specific file paths for compromise indicators are not provided, general areas to investigate include:
wp-content/uploads/for unexpected files.wp-content/plugins/wp-staging/andwp-content/plugins/wp-staging-pro/for altered or new files.The WordPress database for unexpected entries in user metadata or options tables, particularly those related to plugin settings or user profiles.
A command-line check for recently modified files could involve: find . -type f -newermt "YYYY-MM-DD HH:MM:SS" -ls Replace YYYY-MM-DD HH:MM:SS with a timestamp from before the suspected compromise.
How to fix
Check the installed version of the WP STAGING or WP STAGING Pro plugin in the WordPress dashboard under "Plugins". Compare this version with the affected versions listed in the vulnerability record.
If a fixed version (4.18.0 for WP STAGING, 6.18.0 for WP STAGING Pro, or a later release) is available, create a current backup of the entire WordPress site. Then, update the plugin to the fixed version or the latest supported release.
If for any reason a fixed version is not available or an immediate update is not possible, consider disabling and removing the plugin. Explore replacing it with a maintained alternative that provides similar functionality.
After addressing the software vulnerability, thoroughly check the site for any signs of compromise. This includes reviewing for altered administrator users, unexpected file changes, redirects, unfamiliar pages, and reviewing security logs for suspicious activity.
Timeline
Date | Event |
|---|---|
2026-10-09 | WP STAGING Pro 6.17.0 released |
2026-10-18 | WP STAGING Pro 6.18.0 released |
2026-11-18 | NVD entry published |
2026-11-19 | Yuanlong Sec Security Team notes new entry |