Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-19725 – Unauthenticated Path Traversal (Arbitrary Log File Creation) – WPvivid Backup, Migr

Be the first to know when new zero-days emerge:

Summary

CVE-2026-19725 is an unauthenticated path traversal vulnerability (CWE-22) in the WPvivid — Backup, Migration & Staging WordPress plugin. The flaw exists in the send_to_site_connect functionality, which fails to sanitize an attacker-supplied value before using it to build a log file path. It affects all plugin versions prior to 0.9.131 and has been assigned a CVSS v3.1 base score of 9.1 (Critical).

Technical details

  • Root cause: The plugin does not properly sanitize a value taken from an unauthenticated request before using it to construct the path of a log file.
  • Trigger conditions: An attacker in possession of the site’s site-to-site transfer key can invoke the send_to_site_connect functionality remotely, without valid WordPress credentials.
  • Attack vector: Network-based, no authentication or user interaction required (AV:N/PR:N/UI:N).
  • Impact: The attacker can direct the plugin to write a log file into any writable directory on the site, including the web root. The file name carries a fixed suffix and its contents are the plugin’s own fixed log header — attacker control is limited to the file’s location, not its content or name pattern.

Affected software

  • WPvivid — Backup, Migration & Staging (WordPress plugin, published as "Wpvivid Backuprestore") — all versions prior to 0.9.131

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade the WPvivid — Backup, Migration & Staging plugin to version 0.9.131 or later.
  • If patching is not immediately possible: Rotate/invalidate any existing site-to-site transfer keys, restrict or disable the plugin’s remote site-connect feature, and monitor writable web-accessible directories for unexpected log files.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: /wp-content/plugins/wpvivid-backuprestore/

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge