Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-96349 – Unauthenticated Remote Code Execution – SiteSkite WordPress Plugin ≤ 2.1.8

Be the first to know when new zero-days emerge:

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.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge