CVE-2026-109555
validatedZero produced an exploit or a check.GHSA-4v8m-v3r8-w9q4 ↗EUVD-2026-129474 ↗
description
WP STAGING through 4.17.0 and WP STAGING Pro through 6.17.0 can deserialize untrusted data during database restores and staging resets. An authenticated low-privilege user may prepare data that can lead to server-side code execution, local file reading, or, in Pro, file deletion when an administrator later runs a database-including restore or reset.
mitigation
Restrict or remove Subscriber-level and other untrusted accounts, and do not run database-including restores or staging resets containing untrusted user metadata. Review restore sources and profile metadata before administrative restore or reset operations; a fixed release is not recorded in the affected-package data.
outcome
Upstream: a detection for this already ships elsewhere, so we didn't generate a new one. The credit goes to whoever did.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-11-19 05:33Zcve_org: trigger signal, started the run
- 2026-11-19 10:37Z
this entry in the feed
GET /api/v1/feed/CVE-2026-109555
{ "etk_id": "ETK-2026-4916", "cve_id": "CVE-2026-109555", "display_id": "CVE-2026-109555", "ghsa_id": "GHSA-4v8m-v3r8-w9q4", "euvd_id": "EUVD-2026-129474", "status": "published", "anchor_state": "anchored", "title": "PHP object injection in WP STAGING restore workflows", "summary": "WP STAGING through 4.17.0 and WP STAGING Pro through 6.17.0 can deserialize untrusted data during database restores and staging resets. An authenticated low-privilege user may prepare data that can lead to server-side code execution, local file reading, or, in Pro, file deletion when an administrator later runs a database-including restore or reset.", "mitigation": "Restrict or remove Subscriber-level and other untrusted accounts, and do not run database-including restores or staging resets containing untrusted user metadata. Review restore sources and profile metadata before administrative restore or reset operations; a fixed release is not recorded in the affected-package data.", "vendor": "renehermi", "product": "WP STAGING – Backups & Restore, Migration & Clone Plugin – Cloud Backups, Scheduled Backups", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 0, <= 4.17.0" ], "ecosystem": null, "fixed_versions": [], "package_name": "WP STAGING – Backups & Restore, Migration & Clone Plugin – Cloud Backups, Scheduled Backups", "purl": null }, { "affected_notes": [], "affected_ranges": [ ">= 0, <= 6.17.0" ], "ecosystem": null, "fixed_versions": [], "package_name": "WP STAGING Pro WordPress Backup Plugin", "purl": null } ], "cwes": [ 502 ], "cvss_score": 8, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "deterministic", "check": true, "check_confidence_basis": "upstream", "exploit": false, "pipeline_minutes": 0.011378433333333333, "t0_at": "2026-11-19T05:33:21.570000+00:00", "signals": { "check": { "at": "2026-11-19T10:37:18.318618+00:00", "days": 0.211073479375, "is_lower_bound": false, "measured_at": "2026-11-19T05:33:21.570000+00:00", "url": null }, "trigger_signal": { "at": "2026-11-19T05:33:21.570000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-11-19T05:33:21.570000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-109555" } } }
published 2026-11-19 10:37Z
last change 2026-11-19 17:22Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.