Skip to main content
CVE-2026-109555VulnerabilityPublished

The WP STAGING and WP STAGING Pro plugins for WordPress are vulnerable to PHP Object Injection in all versions up to

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-109555· High 8.0

Not known to be exploited · CVSS 8.0 High.

Data as of 19 Nov 2026, 10:50 UTC

CVSS 3.1 base score
8.0High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.18.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
renehermiWP STAGING – Backups & Restore, Migration & Clone Plugin – Cloud Backups, Scheduled BackupsAffected
  • <=4.17.0
Fixed in–
WPStagingWP STAGING Pro WordPress Backup PluginAffected
  • <=6.17.0
Fixed in–

AI-suggested

Until a fix is available, restrict database restore and staging reset operations to trusted administrators only and monitor for suspicious profile metadata modifications. Avoid restoring or resetting staging environments with untrusted data. Follow vendor advisories closely for updates.

Description

The WP STAGING and WP STAGING Pro WordPress plugins contain a PHP Object Injection vulnerability in all versions up to and including 4.17.0 and 6.17.0, respectively. This flaw arises from unsafe deserialization of attacker-controlled input during database restore and staging reset operations. Authenticated users with Subscriber-level access or higher can inject malicious serialized objects into their profiles. When an Administrator later restores or resets the database including this data, arbitrary code execution, local file read, and file deletion can occur. Exploitation requires a privileged restore or reset action by an Administrator but does not require Administrator credentials for the initial injection.

References

Community reviews

Loading reviews…