Security For WooCommerce 1.0.10–1.0.16: The Security Plugin That Lets Strangers Create Administrators (CVE-2026-100109, 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 →

Security For WooCommerce 1.0.10–1.0.16: The Security Plugin That Lets Strangers Create Administrators (CVE-2026-100109, CVSS 9.8)

A plugin with "Security" in its name is supposed to be the thing standing between your store and a stranger. In the Security For WooCommerce plugin for WordPress, at versions 1.0.10 through 1.0.16, that plugin ships an action that creates users — available to unauthenticated visitors, with no capability check, and with the caller choosing the new account's role. That is CVE-2026-100109: unauthenticated administrator creation, scoring CVSS 9.8 — and the CVE record names no patched version yet.

What Happened

CVE-2026-100109 is an unauthenticated privilege-escalation vulnerability in the Security For WooCommerce WordPress plugin, disclosed November 5, 2026 (CNA: WPScan).

Am I Affected?

Check wp-admin → Plugins for a plugin named Security For WooCommerce and its version. At any version from 1.0.10 through 1.0.16, you are in the affected range: a visitor with no account can ask the plugin to create a user — an administrator included.

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 a directory search surfaced no plugin under this exact name — 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 store'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 create users for anyone.
  2. Audit your users. Users → All Users: every Administrator should be a person you can name. This flaw's residue is an account, not an error message — a stranger's administrator account is exactly what a successful exploit leaves behind.
  3. Review recent changes if the affected version was exposed. New administrators can change anything: check orders, payment settings, and files for changes you cannot explain.
  4. When a fix does ship, confirm it names CVE-2026-100109. An update that does not mention this CVE is not evidence this CVE is fixed.

The Bigger Lesson

"Security" in a plugin's name is marketing, not evidence. Any plugin that can create users is holding the keys to the store, whatever its branding — and the code path that creates a user must check, on the server, that the requester already holds a capability that allows it. A missing capability check (CWE-862) on a privileged action is one of the oldest WordPress failure modes there is, and it does not become safer because the plugin around it sells protection. Audit the plugins that hold privileged powers first; their names are the last thing to trust about them.

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 user audit finds a stranger.


Running Security For WooCommerce at 1.0.10–1.0.16? Disable it until a patched release names this CVE and audit your administrators, 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