# CVE-2026-87898: Command injection in Plesk extension "Site Import"

> Remote authenticated users can execute arbitrary code with root privileges via OS command injection in the Plesk Site Import extension.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-q589-mpmp-9796

## What is CVE-2026-87898?

CVE-2026-87898 is a critical command injection vulnerability in WebPros Plesk extension "Site Import", published on 23 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OS command injection in Plesk allows remote authenticated users to execute arbitrary code with root privileges.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-87898 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-87898 is a critical command injection vulnerability in WebPros Plesk extension "Site Import", published on 23 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-87898 in the wild and no public exploit code.

Affected product: WebPros Plesk extension "Site Import". 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-87898/ (Markdown: https://insights.sbomify.com/CVE-2026-87898/index.md)
```

## Sources

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

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