# CVE-2026-93699: Command injection in WP Toolkit

> Local attackers can execute arbitrary code as other accounts via argument injection in WP Toolkit for cPanel.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-fh55-xx6c-9h8v

## What is CVE-2026-93699?

CVE-2026-93699 is a high-severity command injection vulnerability in WebPros WP Toolkit, published on 8 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Argument injection in WP Toolkit for cPanel allows local users to execute arbitrary code as other accounts on the same server.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

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


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

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

## Is CVE-2026-93699 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93699 is a high-severity command injection vulnerability in WebPros WP Toolkit, published on 8 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93699 in the wild and no public exploit code.

Affected product: WebPros WP Toolkit. 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-93699/ (Markdown: https://insights.sbomify.com/CVE-2026-93699/index.md)
```

## Sources

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

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