Static Snapshot ≤ 0.2.1: Unauthenticated Command Execution in a WordPress Plugin (CVE-2026-116533, CVSS 9.8)

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

Static Snapshot ≤ 0.2.1: Unauthenticated Command Execution in a WordPress Plugin (CVE-2026-116533, CVSS 9.8)

A value a visitor types in is meant to be data. In the Static Snapshot plugin for WordPress, at version 0.2.1 and below, that value was concatenated straight into operating-system commands the server runs — shell metacharacters and all. That is CVE-2026-116533: unauthenticated OS command injection via the name parameter, where, in the CVE record's words, the plugin does not sanitise shell metacharacters in a user-supplied value before concatenating it into commands. It scores CVSS 9.8 — and the CVE record names no patched version yet.

What Happened

CVE-2026-116533 is an unauthenticated remote code execution vulnerability in the Static Snapshot plugin for WordPress, disclosed November 6, 2026 (CNA: WPScan).

Am I Affected?

Check wp-admin → Plugins for a plugin named Static Snapshot and its version. At 0.2.1 or below, you are in the affected range: an unauthenticated visitor who can reach the affected function can put shell syntax into a value the server executes.

One honesty note, because it is the whole point of how we cover these: our scanner does not claim a version check for this one. The CVE record names no wordpress.org listing or slug for this plugin, and no listing was verified — so no slug is asserted and no install count is quoted here. Keying a readme check to a guessed slug would produce claims we cannot stand behind in either direction. This article exists because the flaw is real and urgent — not because we can detect it passively. What the free mini-scan can do is check the rest of your site's exposed surface while you handle this one by hand.

What To Do Now

  1. Disable or remove the plugin until the vendor publishes a release naming this CVE. There is no patched version to update to yet. A plugin that is not running cannot concatenate anything into a shell command.
  2. Review server logs and running processes if the affected version was exposed. Command execution leaves different residue than a defaced page: look for processes, cron entries, and outbound connections you cannot explain, and for commands in access logs carrying shell metacharacters in the name parameter.
  3. Audit administrator accounts and uploaded files. Users → All Users: every Administrator should be a person you can name. A host-level execution flaw is exactly the kind that gets quietly converted into persistent access.
  4. When a fix does ship, update and confirm it names CVE-2026-116533. An update that does not mention this CVE is not evidence this CVE is fixed.

The Bigger Lesson

Any plugin that shells out — snapshot tools, backup tools, image and media utilities — lives one unsanitised string away from full host compromise. The rule is not subtle: user input is never part of a command line. Commands are built from fixed program names and fixed argument structures, with values passed as data through APIs that do not invoke a shell at all; the moment a string is concatenated into a command, every metacharacter in it becomes syntax an attacker controls. If a plugin on your site runs external programs, the question worth asking today is whether anything a visitor can type reaches that command as text.

Related: WordPress Hardening for AI-Built Sites — the standing version of this discipline. How to Check If Your Web App Is Hacked — the follow-up pass if the audit finds a stranger.


Running Static Snapshot at 0.2.1 or below? Remove it until a patched release names this CVE, then run the free check at preshipit.com/free-scan — it covers the exposures a scan can see, and articles like this one cover the ones it can't.

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report