WP Toolkit EUVD-2026-94799

Requires the attacker to already hold a valid low-privilege shell/hosting account on the same cPanel server and the ability to invoke WP Toolkit's handler (PR:L, AV:L) - it is NOT remotely exploitable over the network and needs no victim interaction. The core prerequisite is a multi-tenant deployment (shared or reseller hosting) where untrusted local accounts coexist with WP Toolkit installed and reachable by those accounts. The limiting factor is precisely this local-account requirement: a single-tenant server, or one where only trusted operators have accounts, faces little realistic exposure, which substantially narrows real-world risk despite the high impact metrics.

This is a credible mid-to-high priority issue for multi-tenant hosting providers, but not an internet-facing emergency. The provided CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H) is internally consistent with the description: exploitation is LOCAL (AV:L), requires an existing low-privilege account on the box (PR:L), needs no user interaction, and yields full confidentiality/integrity/availability impact - matching 'local users execute arbitrary code as other accounts on the same server' (a cross-account privilege/isolation break via CWE-88 argument injection). No EPSS score, KEV listing, or public POC was provided in the input. There is therefore no evidence of active exploitation: this is NOT in CISA KEV and no public exploit was identified. The 8.5 score is driven by high technical impact and low attack complexity, NOT by remote reach - a security team should weigh it as 'high impact but gated behind local authenticated access,' which realistically scopes it to shared/reseller hosting environments where untrusted users already hold accounts. The main unknown is affected/fixed versions, which the single cPanel advisory reference should clarify but is not present in the structured input.

An attacker who already controls one low-privilege hosting account on a shared cPanel server (e.g. a purchased shared-hosting plan or a compromised customer account) invokes WP Toolkit's handler with maliciously crafted arguments that inject extra command-line parameters. Because the vector is local with low complexity and no user interaction, the injected arguments cause code to run in the context of a different account on the same server, breaking tenant isolation. No public proof-of-concept was identified at the time of analysis.