WP Staging remote code execution in database restore
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
Summary
The WP STAGING and WP STAGING Pro WordPress plugins contain a PHP object injection flaw in their database restore and staging reset code. A remote attacker with at least Subscriber-level login can plant a malicious serialized object in their own profile. When an administrator later runs an ordinary database restore or staging reset that includes it, the object can be used to run arbitrary code on the server, and it can also read local files, with WP STAGING Pro additionally able to delete files.
Written by a model
Original description
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.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by 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…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-109555 (entry last updated 2026-11-19):
Affected:
- renehermi WP STAGING – Backups & Restore, Migration & Clone Plugin – Cloud Backups, Scheduled Backups: through 4.17.0
- WPStaging WP STAGING Pro WordPress Backup Plugin: through 6.17.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-109555 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-109555 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/bf4d6205-3653-4678-86e0-4303a736bb72?source=cve
- https://plugins.trac.wordpress.org/changeset/3753692/wp-staging
- https://wp-staging.com/wp-staging-pro-changelog/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-109555
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-109555"}.Affected versions
- renehermi WP STAGING – Backups & Restore, Migration & Clone Plugin – Cloud Backups, Scheduled Backupsthrough 4.17.0
- WPStaging WP STAGING Pro WordPress Backup Pluginthrough 6.17.0
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity9/10CVSS 8.0, total technical impact per CISA
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 36 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | plugins.trac.wordpress.org · changeset/3753692/wp-staging |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-109555 |
| Record | NVD · CVE-2026-109555 |
| Other links 2 | |
| Link | wordfence.com · threat-intel/vulnerabilities/id/bf4d6205-3653-4678-86e0-4303a736bb72?source=cve |
| Link | wp-staging.com · wp-staging-pro-changelog |
Questions about CVE-2026-109555
Is CVE-2026-109555 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-109555?
WP STAGING – Backups & Restore, Migration & Clone Plugin – Cloud Backups, Scheduled Backups: through 4.17.0. WP STAGING Pro WordPress Backup Plugin: through 6.17.0.
Source: cve.now feed data
Related
- CVE-2024-5551WP STAGING PRO - Backup Duplicator & Migration <= 5.6.0 - Cross-Site Request Forgery to Limited Local File Inclusion
- CVE-2025-3104WP Staging Pro <= 6.1.2 - Unauthenticated Information Exposure via getOutdatedPluginsRequest Function
- CVE-2024-3682WP STAGING <= 3.4.3 and WP STAGING Pro <= 5.4.3 - Sensitive Information Exposure via Log File
- CVE-2026-115871WP STAGING <= 4.19.0 - Authenticated (Administrator+) Arbitrary Directory Deletion via 'deleteDir' Parameter
- CVE-2024-3412WP STAGING WordPress Backup Plugin – Migration Backup Restore <= 3.4.3 - Authenticated (Admin+) Arbitrary File Upload
- CVE-2026-114824Vulnerability in the Oracle Platform Security for Java product of Oracle Fusion Middleware (component: Centralized Thirdparty Jars).
No corrections so far. Something wrong on this page? Report an error.