CVE-2026-101889

Prime Mover – Backup and Migration <= 2.2.0 - Authenticated (Admin+) Arbitrary Directory Deletion

2026-10-01 00:00
Sarvar Eshboyev

Strategic Overview

Status
Patched in 2.2.1
Affected Version
<= 2.2.0
CVSS
7.1High
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2026-101889
View all Prime Mover – Backup and Migration vulnerabilities

At a glance

CVE-2026-101889 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Prime Mover WordPress plugin, affecting versions <= 2.2.0. It carries a CVSS score of 7.1 (reachable over the network; low attack complexity; high availability impact). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 2.2.1; sites on affected versions should update now. Disclosed October 2026, reported by Sarvar Eshboyev.

Vulnerability Overview

The Prime Mover – Backup and Migration plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 2.2.0. This is due to insufficient validation of a user supplied path. This makes it possible for authenticated attackers to delete directories outside of the intended directory.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on availability.

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Reaching this weakness in Prime Mover <= 2.2.0 takes an account at Admin level or above. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.

Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For Prime Mover the fix is 2.2.1: builds <= 2.2.0 are affected, anything from 2.2.1 onward is not.

Remediation

Update to version 2.2.1, or a newer patched version

How does WordSec protect against this?

An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Prime Mover 2.2.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C