CVE
Backup Migration remote code execution in PclZip restore fallback
- Exploited
- No known exploitation
- Fix
- Fixed in 2.1.8
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Backup Migration plugin before 2.1.8 for WordPress Server lacks the PHP zip extension, so the PclZip restore fallback is used An administrator restores a malicious backup archive
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.47% · 41st percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Backup Migration by inisev for WordPress has a path traversal flaw in its restore fallback that lets an attacker write files outside the intended folder, which can lead to remote code execution. Exploitation is reached over the network but requires high-level access and an administrator to restore a malicious backup archive, on a server that lacks the PHP zip extension.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Backup Migration before 2.1.8 for WordPress contains a path traversal vulnerability in its PclZip restore fallback that allows an attacker to achieve arbitrary file write when an administrator restores a malicious backup archive on a server lacking the PHP zip extension. Attackers can craft a zip archive with entry names containing ".." sequences, which PclZip's extract() processes without the PCLZIP_OPT_EXTRACT_DIR_RESTRICTION option, writing a PHP file outside the intended extraction directory into the web-servable tree to achieve remote code execution.
Who should check
Teams running the Backup Migration WordPress plugin before 2.1.8, especially hosts without the PHP zip extension where administrators restore backup archives.
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.1/10CVSS 7.1, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Backup Migration plugin before 2.1.8 for WordPress Server lacks the PHP zip extension, so the PclZip restore fallback is used An administrator restores a malicious backup archiveUpgrade to a fixed version: 2.1.8.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-127050 (Backup Migration before 2.1.8 Path Traversal via PclZip Restore Fallback), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-127050 (entry last updated 2026-11-12):
Affected:
- inisev Backup Migration: fixed in 2.1.8
Fixed versions: 2.1.8.
Conditions (all must be true for the bug to be hit):
- Backup Migration plugin before 2.1.8 for WordPress (source: https://www.vulncheck.com/advisories/backup-migration-before-path-traversal-via-pclzip-restore-fallback)
- Server lacks the PHP zip extension, so the PclZip restore fallback is used (source: https://www.vulncheck.com/advisories/backup-migration-before-path-traversal-via-pclzip-restore-fallback)
- An administrator restores a malicious backup archive (source: https://www.vulncheck.com/advisories/backup-migration-before-path-traversal-via-pclzip-restore-fallback)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, a user action.
CISA KEV: CVE-2026-127050 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-127050 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://wordpress.org/plugins/backup-backup/#developers
- https://www.vulncheck.com/advisories/backup-migration-before-path-traversal-via-pclzip-restore-fallback
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-127050
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-127050"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- inisev Backup Migration
fixed in 2.1.8
Evidence 4
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-127050
Is CVE-2026-127050 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The plugin's restore step does not properly limit where files from a backup archive are written, so a crafted archive can make it write files outside the intended folder. Per the facts, this can place a PHP file in the web-servable tree, which can lead to remote code execution.Source: vulncheck.com
Which versions are affected by CVE-2026-127050?
Backup Migration: before 2.1.8.Source: cve.now feed data
Am I affected, and how do I check?
Backup Migration versions before 2.1.8 for WordPress are affected, but only on servers that lack the PHP zip extension, where the PclZip restore fallback is used, and only when an administrator restores a malicious backup archive. To check, look at the plugin version in the WordPress plugins screen and check whether the PHP zip extension is loaded (for example, with the phpinfo output or the php -m command).Source: vulncheck.com
How do I fix CVE-2026-127050?
Upgrade Backup Migration to version 2.1.8 or later, which is the fixed version listed for this vulnerability.Source: vulncheck.com