Summary
CVE-2026-96349 is a critical, unauthenticated Remote Code Execution (RCE) vulnerability in the SiteSkite WordPress plugin, affecting all versions up to and including 2.1.8. The flaw is classified as CWE-94 (Improper Control of Generation of Code / "Code Injection") and carries the maximum CVSS v3.1 base score of 10.0. Because no authentication or user interaction is required, any internet-facing WordPress site running a vulnerable version of SiteSkite is exposed to full server compromise.
Technical details
- Root cause: Improper control of code generation (CWE-94) within the SiteSkite plugin allows an attacker-supplied input to be executed as code by the WordPress/PHP runtime (CAPEC-253 – Remote Code Inclusion).
- Trigger conditions: The vulnerable code path is reachable pre-authentication, requiring no valid WordPress account, API key, or user session.
- Attack vector: Network — the vulnerability can be exploited remotely over HTTP(S) against the WordPress site’s exposed endpoints, with low attack complexity and no user interaction.
- Impact: Successful exploitation grants an unauthenticated remote attacker the ability to execute arbitrary code on the underlying server, resulting in complete loss of confidentiality, integrity, and availability. The CVSS "Scope: Changed" designation reflects that the impact extends beyond the vulnerable component to the broader WordPress/server environment.
- Product context: SiteSkite is a WebOps/management plugin for WordPress that provides site backups, sandboxing, bulk updates, monitoring, and AI-agent connectivity (via the Model Context Protocol) for managing one or many sites — functionality that typically requires elevated server-level access, amplifying the potential blast radius of code execution flaws.
Affected software
- Product: SiteSkite (WordPress plugin), vendor: SiteSkite
- Vulnerable versions: All versions ≤ 2.1.8
- Fixed version: 2.2.0 and later
Severity
- CVSS v3.1 Base Score: 10.0 (Critical)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: Update the SiteSkite plugin to version 2.2.0 or later, which remediates the vulnerability.
- If immediate patching is not possible:
- Take affected WordPress sites offline or restrict access to them via a WAF/reverse proxy until the update can be applied.
- Disable or deactivate the SiteSkite plugin entirely until it can be updated.
- Audit WordPress installations for unexpected admin users, unfamiliar files, or scheduled tasks that could indicate prior exploitation, given the vulnerability has been publicly disclosed with mass-exploitation potential.
- Review server and WordPress access logs for anomalous, unauthenticated requests to SiteSkite plugin endpoints.

