# CVE-2026-1357: Migration, Backup, Staging <= 0.9.123 - Unauthenticated Arbitrary File Upload

> Unauthenticated attackers can upload arbitrary PHP files to achieve remote code execution due to improper error handling and lack of path sanitization.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-3cvp-fw5m-7w6r

## What is CVE-2026-1357?

CVE-2026-1357 is a critical vulnerability in wpvividplugins WPvivid — Backup, Migration & Staging, published on 11 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Migration, Backup, Staging – WPvivid Backup & Migration plugin for WordPress is vulnerable to Unauthenticated Arbitrary File Upload in versions up to and including 0.9.123. This is due to improper error handling in the RSA decryption process combined with a lack of path sanitization when writing uploaded files. When the plugin fails to decrypt a session key using openssl_private_decrypt(), it does not terminate execution and instead passes the boolean false value to the phpseclib library's AES cipher initialization. The library treats this false value as a string of null bytes, allowing an attacker to encrypt a malicious payload using a predictable null-byte key. Additionally, the plugin accepts filenames from the decrypted payload without sanitization, enabling directory traversal to escape the protected backup directory. This makes it possible for unauthenticated attackers to upload arbitrary PHP files to publicly accessible directories and achieve Remote Code Execution via the wpvivid_action=send_to_site parameter.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2026-1357?


## How do I fix CVE-2026-1357?

No fix has been published for CVE-2026-1357 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-1357 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1357 exists.

Public exploit code:

- CVE-2026-1357 — WPvivid Backup & Migration ≤ 0.9.123 Unauthenticated RCE Exploit (github_poc): https://github.com/halilkirazkaya/CVE-2026-1357
- POC-CVE-2026-1357 (github_poc): https://github.com/LucasM0ntes/POC-CVE-2026-1357
- https://github.com/cybertechajju/CVE-2026-1357-POC (github_poc): https://github.com/cybertechajju/CVE-2026-1357-POC
- Exploit CVE-2026-1357 (github_poc): https://github.com/itsismarcos/Exploit-CVE-2026-1357
- Migration, Backup, Staging <= 0.9.123 - Unauthenticated Arbitrary File Upload (github_poc): https://github.com/Nxploited/CVE-2026-1357
- https://github.com/sahmsec/CVE-2026-1357 (github_poc): https://github.com/sahmsec/CVE-2026-1357

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1357 and fix it if it is affected.

What it is: CVE-2026-1357 is a critical vulnerability in wpvividplugins WPvivid — Backup, Migration & Staging, published on 11 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1357 exists.

Affected product: wpvividplugins WPvivid — Backup, Migration & Staging. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1357/ (Markdown: https://insights.sbomify.com/CVE-2026-1357/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1357
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1357
- OSV: https://osv.dev/vulnerability/CVE-2026-1357

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1357/
Summaries are generated and may contain mistakes; the official description above is the record.