WP STAGING and WP STAGING Pro: subscriber-planted serialized object can run code when an administrator later restores or resets
Identifiers: CVE-2026-109555
- Published
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
Summary
Wordfence published on 18 November 2026 a PHP object injection in WP STAGING Free up to 4.17.0 and WP STAGING Pro up to 6.17.0 (CVE-2026-109555). The database importer treats text beginning with {WPSTG_BINARY} as trusted internal binary data and decodes its hexadecimal suffix into serialized bytes. A Subscriber-level user can store such text in their own profile. If an administrator later performs an ordinary database-including restore or staging reset that contains that value, and the restored profile metadata is loaded, either during the restore or in a later request, a built-in gadget chain can execute arbitrary code.
Impact
Remote code execution on the server. Built-in chains also allow arbitrary local file read in both editions and arbitrary file deletion in Pro only. The attacker needs no administrator credentials and no copy of a backup, but exploitation does depend on a later privileged restore or reset.
Who is affected
WordPress sites running WP STAGING Free 4.17.0 or earlier, or Pro 6.17.0 or earlier, that have untrusted low-privilege accounts and use database restore or staging reset. This is a different plugin and CVE from the recently covered UpdraftPlus issue, and it is not a WordPress core fix.
Products and versions
| Products and versions | Affected | Fixed |
|---|---|---|
| WP STAGING Free | <=4.17.0 | 4.18.0 or later; researcher-recommended first fixed version |
| WP STAGING Pro | <=6.17.0 | 6.18.0 or later; researcher-recommended first fixed version |
Exploitation evidence
Exploitation not established. No exploitation established. Requires a subscriber account plus a later administrator restore or reset; this is not an instant unauthenticated attack.
Actions
- Update to a current maintained release that is at least 4.18.0 (Free) or 6.18.0 (Pro). Do not downgrade to those floors if you already run something newer.
- Keep known-good backups and test restores in an isolated, already-updated environment before relying on them in production.
- Before your next restore or staging reset, review subscriber and other low-privilege accounts for unexpected profile content.
Unknowns
- Whether backups taken before the fix are handled safely by the patched importer is not stated; do not assume older backups are safe.
- The vendor's 18 October 2026 changelogs confirm 4.18.0 and 6.18.0 as security hardening releases but do not map them to this CVE; the CNA record returned 404 when checked.
- No exploitation in the wild has been established.
Sources
- Wordfence Intelligence https://www.wordfence.com/threat-intel/vulnerabilities/detail/wp-staging-4170-and-wp-staging-pro-6170-authenticated-subscriber-php-object-injection-to-remote-code-execution-via-database-restore-and-staging-reset
- WP STAGING https://wp-staging.com/wp-staging-changelog/
- WP STAGING https://wp-staging.com/wp-staging-pro-changelog/
Change history
- — Published: Published 19 November 2026. Wordfence disclosed CVE-2026-109555 on 18 November 2026; the vendor's 18 October 2026 changelogs list the 4.18.0 (Free) and 6.18.0 (Pro) security hardening releases.