Skip to content
Web

CVE-2026-19725

9.1
Critical
EPSS 0.37%Patch availableAug 18, 2026

Path traversal in WPvivid plugin lets attacker create log files in writable directories.

common questions

Is CVE-2026-19725 being exploited?

Not confirmed. CVE-2026-19725 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.37% probability of exploitation in the next 30 days.

How severe is CVE-2026-19725?

CVE-2026-19725 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-19725?

Yes. A fix has been recorded for CVE-2026-19725. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-19725 affect?

CVE-2026-19725 affects WPvivid — Backup, Migration & Staging WordPress plugin < 0.9.131, WordPress sites using WPvivid. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-19725?

Update WPvivid to 0.9.131+; restrict writable web directories and audit web root.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
WPvivid — Backup, Migration & Staging WordPress plugin < 0.9.131WordPress sites using WPvivid
impact

Attacker with a site-to-site transfer key can create files in any writable directory (including web root), enabling hosted files, overwrite of writable files, persistence or defacement.

action required

Immediate action required

affected versions
Unknown WPvivid — Backup, Migration & Staging
  • affected< 0.9.131

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free