CVE-2026-1357
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe WPvivid plugin fails to properly handle errors in RSA decryption - when openssl_private_decrypt() returns false, execution continues and passes this boolean to phpseclib's AES cipher, which interprets it as a null-byte key. Combined with missing path sanitization on filenames from the decrypted payload, unauthenticated attackers can upload arbitrary PHP files to public directories via the wpvivid_action=send_to_site parameter.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- 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
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify WPvivid plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and locate 'WPvivid Backup & Migration'. Check the version number displayed under the plugin name. Alternatively, check the plugin's main PHP file (wpvivid-backuprestore.php) for the 'Version' header comment, or use a database query on the wp_options table for option_name 'wpvivid_plugin_version'Affected if The installed version is 0.9.123 or lower, or if the plugin is installed but no version information is found (unknown versions should be treated as potentially vulnerable)
-
Confirm plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and verify that WPvivid Backup & Migration shows as 'Active'Affected if The plugin is active and the version is 0.9.123 or lower, making the vulnerability exploitable
-
Inspect publicly accessible upload directories for suspicious PHP filesCheck directories such as /wp-content/uploads/, /wp-content/, /wp-includes/, and any custom upload paths for unfamiliar .php files. Use file system commands: 'find /path/to/wordpress/wp-content -name "*.php" -mtime -30' to find recently modified PHP files, or manually review directory listingsAffected if Any unknown or suspicious PHP files exist in web-accessible directories, especially if they were recently created and contain base64 encoded content or web shells
-
Review access logs for exploitation attemptsExamine web server access logs (Apache error/access logs, Nginx access logs) for requests containing 'wpvivid_action=send_to_site' parameter, particularly those with directory traversal patterns like '../' in filenames or unusual base64-encoded payloadsAffected if Log entries show requests to 'wpvivid_action=send_to_site' with directory traversal sequences or attempts to upload .php files to non-plugin directories
The environment is affected if WPvivid Backup & Migration plugin version 0.9.123 or lower is installed and active, or if unknown PHP files exist in web-accessible directories or exploitation attempts appear in logs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate the WPvivid plugin to the latest version immediately. If patching is not possible, disable the plugin or block the wpvivid_action parameter at the web application firewall level.
Latest version after 0.9.123 (check WordPress plugin repository for current stable release)
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'WPvivid Backup & Migration' in the plugin list
- If an update is available, click 'Update Now' to install the latest version
- Alternatively, navigate to Dashboard > Updates and select the plugin to update
- After updating, verify the new version number in the plugins list
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1357 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1357 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data