# CVE-2026-101889: Prime Mover < 2.2.1 Path Traversal via wprime-config.json

> Authenticated administrators can delete arbitrary directories, including critical WordPress files, via path traversal in the Prime Mover plugin.

- **Severity:** High 7.0 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-73vx-gw2c-25gg

## What is CVE-2026-101889?

CVE-2026-101889 is a high-severity path traversal vulnerability in Codexonics Prime Mover, published on 1 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-101889?


## How do I fix CVE-2026-101889?

No fix has been published for CVE-2026-101889 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-101889 being exploited?

There is no known exploitation of CVE-2026-101889 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-101889 and fix it if it is affected.

What it is: CVE-2026-101889 is a high-severity path traversal vulnerability in Codexonics Prime Mover, published on 1 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-101889 in the wild and no public exploit code.

Affected product: Codexonics Prime Mover. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-101889/ (Markdown: https://insights.sbomify.com/CVE-2026-101889/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-101889
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-101889
- OSV: https://osv.dev/vulnerability/CVE-2026-101889

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-101889/
Summaries are generated and may contain mistakes; the official description above is the record.