Read the docs

Arbitrary directory deletion in WP STAGING plugin for WordPress

Priority LOW 14CWE-73Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
None · Low · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

The WP STAGING plugin by renehermi is affected in all versions up to and including 4.19.0. Insufficient path validation in the cleanStagingDirectory function does not remove traversal sequences or keep deletion inside the staging directory (CWE-73). An authenticated attacker with administrator access can recursively delete arbitrary directories on the server, causing denial of service or permanent data loss.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

The WP STAGING – Backups & Restore, Migration & Clone Plugin – Cloud Backups, Scheduled Backups plugin for WordPress is vulnerable to Arbitrary Directory Deletion in all versions up to, and including, 4.19.0. This is due to insufficient path validation in the `cleanStagingDirectory` function, where the `deleteDir` parameter is only stripped of whitespace and double slashes by `sanitizePath()` without removing `..` traversal sequences or enforcing containment within the staging directory, leaving the sole pre-deletion guard as a simple string equality check against the WordPress home path. This makes it possible for authenticated attackers, with administrator-level access and above, to recursively delete arbitrary directories on the server — including `wp-content`, `wp-admin`, or directories outside the WordPress installation on shared hosting — resulting in denial of service or permanent data loss. An attacker must sequence a clone start, cancellation, and restart to drive the `delete_job` cache into the `directory` step before re-cancelling with a manipulated `deleteDir` value supplied via the `wp_ajax_wpstg_cancel_clone` endpoint.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00405 35th percentileScored 2026-11-16
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
renehermiWP STAGING – Backups & Restore, Migration & Clone Plugin – Cloud Backups, Scheduled Backupsup to 4.19.0—No fix listedCNA
  • WP STAGING – Backups & Restore, Migration & Clone Plugin – Cloud Backups, Scheduled Backups Vendorrenehermi Affected up to 4.19.0 Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for WP STAGING.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-115871
  2. 2026-11-13 Alias added: GHSA-xv55-82wc-8j27
  3. 2026-11-13 CISA SSVC decision points changed

References

  • TI-2024-03182 WP STAGING WordPress Backup Plugin – Migration Backup Restore <= 3.4.3 - Authenticated (Admin+) Arbitrary File Upload CVSS 3.1CRITICAL 9.1
  • TI-2024-03436 WP STAGING <= 3.4.3 and WP STAGING Pro <= 5.4.3 - Sensitive Information Exposure via Log File CVSS 3.1MEDIUM 5.3

Sources