Skip to main content

Prime Mover CVE-2026-101889

| EUVDEUVD-2026-90913 HIGH
Path Traversal (CWE-22)
2026-10-01 VulnCheck GHSA-73vx-gw2c-25gg
7.0
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain WordPress admin access
  2. Delivery
    Craft WPRIME/TAR with malicious tar_root_folder
  3. Exploit
    Import package via Prime Mover
  4. Execution
    Bypass path validation in extract logic
  5. Persist
    Delete directories outside extraction path
  6. Impact
    Remove wp-admin and break site

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK

2 techniques across 2 tactics: Discovery, Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires an authenticated WordPress administrator account (CVSS PR:H) who imports a crafted WPRIME/TAR package containing a wprime-config.json with manipulated tar_root_folder values; the Prime Mover plugin (before 2.2.1) must be installed and the import feature used. Exploitation is limited by the need for administrator-level privileges - this cannot be triggered by unauthenticated or low-privileged users - and by requiring the victim to perform (or be tricked into performing) the malicious package import. No user interaction beyond the admin's own import action is needed (UI:N). Default configurations are affected once the plugin is present and an admin imports a package.

Impact

This is a moderate, not top-tier, priority. The CVSS 4.0 base score of 7.0 is driven by integrity and availability impact (VI:H/VA:H) with no confidentiality loss (VC:N), and critically requires high privileges (PR:H) - only an authenticated WordPress administrator can trigger it by importing a crafted WPRIME/TAR package. The attack vector is network (AV:N) and complexity is low (AC:L, AT:N) once admin access is held, but PR:H is the dominant mitigating factor: an administrator already has legitimate power to damage a site, so this vulnerability primarily matters for compromised/abused admin accounts or multi-admin environments where a lower-trust admin should not be able to destroy the filesystem. No EPSS score, KEV listing, or POC was provided in the input, and there is no public exploit identified at time of analysis, indicating no evidence of widespread or active exploitation. The signals are internally consistent - there is no CVSS-vs-description conflict here; the description's 'authenticated administrators' aligns with PR:H. Net: a real, patch-worthy integrity/availability bug, but the admin-privilege precondition keeps real-world risk well below that of an unauthenticated RCE.

Exploit ScenarioDerived

An attacker who has obtained WordPress administrator access (e.g., via phishing, credential reuse, or a lower-trust admin on a shared multi-admin site) crafts a malicious WPRIME/TAR backup package whose wprime-config.json contains manipulated tar_root_folder values. Upon importing it through Prime Mover, insufficient path validation in computeExtractVariables() and validateImportedSiteVsPackage() causes primeMoverDoDelete() to remove directories outside the extraction path - such as wp-admin - rendering the site inoperable. No public exploit code was identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 01, 2026

Authenticated WordPress administrators can abuse the Prime Mover plugin before 2.2.1 to delete arbitrary directories outside the intended extraction path by importing a crafted WPRIME/TAR package whose wprime-config.json contains manipulated tar_root_folder values, ultimately tricking primeMoverDoDelete() into removing critical directories such as wp-admin, which can render the site inoperable. Exploitation requires a high-privileged WordPress administrator account (CVSS PR:H) that performs the package import, so this is not reachable by unauthenticated or low-privileged users; no user interaction beyond the admin's own import action is required. This is a moderate, not top-tier, priority issue: no public exploit code has been identified and there is no CISA KEV listing, though the confidentiality impact is nil while integrity and availability impacts are high, and the vendor has released a fix in version 2.2.1.

RemediationAI

Upgrade the Prime Mover plugin to version 2.2.1 or later - the vendor-released patch fixes the path traversal in computeExtractVariables() and validateImportedSiteVsPackage() and is available from the WordPress plugin page at https://wordpress.org/plugins/prime-mover/#developers; after updating, verify the installed version in the WordPress Plugins screen and clear any cached plugin artifacts. Until the update is applied, treat the import feature as a privileged destructive operation: only import WPRIME/TAR packages produced by a trusted, verifiable source, and inspect the archive's wprime-config.json for suspicious tar_root_folder values containing traversal sequences before import, recognizing that manual inspection is error-prone and is not a substitute for patching. Compensating controls include temporarily deactivating Prime Mover when its import/export capability is not needed (removing the attack surface entirely but losing the plugin's migration functionality), restricting administrator-level accounts to a minimal trusted set and removing dormant admins so the PR:H prerequisite is harder to satisfy, and placing strict access controls (for example IP allowlisting or HTTP authentication) in front of wp-admin to reduce the chance an attacker obtains the required credentials. Because exploitation results in recursive directory deletion, maintain tested off-site backups and file-integrity monitoring, particularly of wp-admin and wp-content, so a successful or attempted traversal delete can be detected and recovered quickly; note that file-integrity scanning and backups are detective and recovery measures only and do not block the deletion itself. Additional details are available in the VulnCheck advisory at https://www.vulncheck.com/advisories/prime-mover-path-traversal-via-wprime-config-json.

Affected VersionsENISA

Prime Mover 0 <2.2.1

Affected Packages

euvd prime_mover fix: 2.2.1

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-22 (Improper Limitation of a Pathname to a Restricted Directory / Path Traversal) in the WordPress Prime Mover plugin, tracked against the CPE cpe:2.3:a:codexonics:prime_mover:*:*:*:*:*:*:*:*, which denotes all plugin releases prior to the fixed version. Prime Mover exports and imports site packages in a WPRIME/TAR archive format, and the archive carries a configuration file named wprime-config.json that supplies metadata such as tar_root_folder, which the plugin uses to decide where extracted content should be rooted and which paths are safe to clean up. The plugin's computeExtractVariables() and validateImportedSiteVsPackage() routines reportedly fail to adequately validate or canonicalize the attacker-supplied tar_root_folder value, so path sequences that escape the intended extraction directory are accepted as legitimate. Because the same value is later consumed by primeMoverDoDelete(), a recursive delete operation intended only for the plugin's own extraction workspace can be redirected to arbitrary paths, including core WordPress directories like wp-admin. The vector is network-reachable (AV:N) with low attack complexity (AC:L) and no user interaction (UI:N), but the attacker must hold administrator privileges (PR:H) and must supply the malicious package through the import workflow, meaning the flaw is a privileged-feature trust-boundary failure rather than an unauthenticated remote exploit.

Know when Prime Mover gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 7.0 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 6.5 MEDIUM

Exploitation requires administrator privileges so PR:H; network-reachable import with low complexity (AV:N/AC:L); arbitrary directory deletion gives I:H/A:H and no data disclosure (C:N).

3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
High
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

The Prime Mover plugin for WordPress before 2.2.1 contains a path traversal vulnerability that allows authenticated administrators to delete arbitrary directories by importing a crafted WPRIME/TAR package with manipulated tar_root_folder values in wprime-config.json. Attackers can exploit insufficient path validation in computeExtractVariables() and validateImportedSiteVsPackage() to cause primeMoverDoDelete() to remove directories outside the intended extraction path, potentially deleting critical WordPress directories such as wp-admin and rendering the site inoperable.

Executive ViewAI

Why It Matters

The Prime Mover plugin for WordPress, used for site migration and backup, contains a high-severity vulnerability that could allow a malicious or compromised administrator to delete essential files, causing significant website downtime. Organizations using this plugin face potential operational disruption and data loss, though the need for administrative credentials limits the threat to insider or credential-compromise scenarios. Leadership should prioritize updating to version 2.2.1 to prevent service outages that could impact customer trust and business continuity.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 74% exploitable
Prevalence
Low
niche WordPress migration/backup plugin, modest install base
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Medium
Technical Impact
Partial

Priority Score

35
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +35
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy