Migration, Backup, Staging – WPvivid

The WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.138 does not properly validate a backup storage directory path before using it to create directories and write files, allowing administrators to cause those directories and files to be created outside the intended backup location via path traversal. The structured affected range is < 0.9.138.

The WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.137 does not validate the extension of the file it actually stores when handling an import upload: it checks the extension of a separate request field while saving the uploaded file itself with WordPress's upload type-checking disabled, so an authenticated administrator can store a file with an arbitrary extension, including a PHP file, in the WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.137's import directory. This is an incomplete fix of CVE-2025-5961, whose extension check was applied to the wrong value. The structured affected range is 0.9.117 to < 0.9.137.

The WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.137 does not sanitize the staging destination folder supplied to its staging-start handler, applying only a generic text filter while the sibling writability-check handler applies the correct filename sanitizer, so an authenticated administrator can supply a path containing traversal sequences and make the WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.137 write the copied site files outside the WordPress installation directory. The structured affected range is < 0.9.137.

The WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.137 does not verify that a submitted snapshot identifier names a snapshot it actually created before using it as a database table-name prefix, so an authenticated administrator can supply the site's table prefix, or any other string, and cause the WPvivid — Backup, Migration & Staging WordPress plugin before 0.9.137 to drop every matching table, including the core WordPress tables, destroying the site's database. The structured affected range is < 0.9.137.

WPvivid before 0.9.133 places an administrator-supplied list of identifiers into a database query without adequate sanitization, allowing an Administrator to perform SQL injection.

WPvivid Backup and Migration before 0.9.131 accepts attacker-controlled path data during a site-to-site transfer and uses it when creating a transfer log. A remote requester must possess a valid site-to-site transfer key, but can then traverse into any existing directory writable by PHP and create the plugin's fixed-name log file there. Only the location is controlled: the filename suffix and log header are fixed, and.

WPvivid through 0.9.131 accepts export_data JSON object keys in prepare_export_post(), stores them as post IDs without integer casting, then joins them into an unquoted WHERE ID IN clause in export_post_to_xml(). An Administrator can inject SQL through those keys and extract database information.

WPvivid — Backup, Migration & Staging is affected by arbitrary file deletion. Exploitation requires an authenticated administrator account. A successful request can remove files outside the intended scope and may make the site unavailable. The published affected range is <= 0.9.128.

Migration, Backup, Staging – WPvivid Backup & Migration is affected by dangerous file upload. The vulnerable path is reachable without authentication. Successful exploitation can place attacker-controlled executable content on the server and may lead to full site compromise.

Migration, Backup, Staging – WPvivid Backup & Migration is affected by a security weakness. Exploitation requires an authenticated administrator account. The resulting impact depends on how the affected component exposes the vulnerable operation.

Migration, Backup, Staging – WPvivid Backup & Migration is affected by dangerous file upload. Exploitation requires an authenticated administrator account. Successful exploitation can place attacker-controlled executable content on the server and may lead to full site compromise.

Migration, Backup, Staging – WPvivid is affected by code execution. The vulnerable path is reachable without authentication. Successful exploitation can run attacker-controlled code in the WordPress hosting account.

WPvivid Backup and Migration is affected by privilege escalation or authentication bypass. Exposure depends on how the affected operation is made reachable by the site. A successful request can grant permissions or access that the caller should not possess.

WPvivid is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.

Migration, Backup, Staging - WPvivid is affected by sensitive information exposure. The vulnerable path is reachable without authentication. Successful exploitation can disclose data that should not be available to the caller.

Migration, Backup, Staging – WPvivid is affected by cross-site scripting. Exploitation requires an authenticated WordPress account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

Migration, Backup, Staging – WPvivid is affected by filesystem traversal. Exploitation requires an authenticated WordPress account. A crafted path can escape the intended directory and reach files or directories elsewhere on the server.

Migration, Backup, Staging – WPvivid is affected by code execution. Exploitation requires an authenticated WordPress account. Successful exploitation can run attacker-controlled code in the WordPress hosting account.

Wpvivid Backuprestore is affected by filesystem traversal. Exposure depends on how the affected operation is made reachable by the site. A crafted path can escape the intended directory and reach files or directories elsewhere on the server.