Vulnerability

Security For WooCommerce Admin Account Creation Flaw (CVE-2026-100109)

CVE ID
CVE-2026-100109
CVSS
9.8 Critical (CVSS v3.0, WPScan as CNA; NVD lists it as a secondary source); no CVSS 3.1 or 4.0 score in the record or NVD
Affected product
Security For WooCommerce plugin 1.0.10 through 1.0.16, per the CVE record
Exploited
Unknown
Published
5 November 2026 (CVE record and NVD)

In short

CVE-2026-100109 is a missing-authorization flaw in the Security For WooCommerce WordPress plugin, versions 1.0.10 to 1.0.16, that lets an unauthenticated visitor create an administrator account. WPScan, the CNA, scores it CVSS 3.0 9.8 and lists no known fix.

Profile MapVulnerability
  1. CVECVE-2026-100109
  2. ProductUnknown in the CVE record (plugin author listed on WordPress.org as Rizvi) Security For WooCommerce plugin 1.0.10 through 1.0.16, per the CVE record
  3. Fix Steps5actions listedFind the Plugin on Every Site · Deactivate and Remove It

What it allows

CVE-2026-100109 affects the Security For WooCommerce plugin, versions 1.0.10 to 1.0.16. The CVE record says the plugin does not check capabilities when it creates users through an action available to unauthenticated visitors. It also lets the caller choose the new account's role. An attacker can therefore ask for an administrator account and take over the site.

The record files the weakness under CWE-862, Missing Authorization. WPScan's own entry classifies it as privilege escalation under CWE-269. The record title names usfw_create_temporary_user as the affected function. The record does not describe how that action is reached or which request triggers it.

In WordPress, an administrator can install plugins and edit theme files, which usually means code execution on the server. That is why a flaw that hands out administrator accounts is rated as a full site takeover. This reading is ours; the record states only that attackers can create administrator accounts and take over the site.

What WPScan and the Plugin Directory Say

WPScan, the CNA, lists the finder as Afan and shows the entry as publicly published on 3 November 2026. Its page says the proof of concept will be displayed on 1 February 2027 to give users time to update. It also states that there is no known fix.

The WordPress.org plugin page says the plugin was closed on 13 October 2026 and is not available for download. It calls the closure temporary, pending a full review. Sites that installed the plugin earlier keep running it, and we recommend treating them as exposed.

What the Scores and CISA KEV Say

The record carries a CVSS 3.0 score of 9.8 Critical from WPScan, with vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. NVD lists that score as secondary and received the entry on 5 November 2026 without its own analysis yet. There is no CVSS 3.1 or 4.0 score in the record or NVD.

As of CISA catalog version 2026.11.04, the CVE is not in the Known Exploited Vulnerabilities catalog. Our KEV glossary entry explains what the catalog covers and how to read it.

Who is affected

The CVE record lists the Security For WooCommerce plugin from 1.0.10 through 1.0.16, as a single semver range. The record gives the vendor as Unknown and the default status as unknown. WPScan lists the WordPress.org plugin slug as ultimate-security-for-woocommerce, which is the name to search for on your sites.

The record names no versions before 1.0.10, and we do not read that as proof that earlier releases are safe. We recommend removing the plugin on any version until the author publishes a fixed release. Our vulnerability management guide covers how to track a plugin with no patch.

The WordPress exposure check can help you review what a public WordPress site reveals about its plugins and versions. Run it alongside an internal inventory, because the plugin may be inactive but still installed.

Timeline

  1. 25 Sep 2026

    WPScan reserves CVE-2026-100109 (CVE record).

  2. 13 Oct 2026

    WordPress.org closes the plugin pending a full review (plugin page).

  3. 3 Nov 2026

    WPScan lists the vulnerability as publicly published.

  4. 5 Nov 2026

    The CVE record is published and NVD receives the entry.

What to do

  1. Find the Plugin on Every Site

    Search each WordPress and WooCommerce site for the slug ultimate-security-for-woocommerce, shown as Security For WooCommerce in the admin.

  2. Deactivate and Remove It

    WPScan lists no known fix and WordPress.org has closed the plugin. We recommend deactivating and deleting it until the author ships a fixed release.

  3. Audit Administrator Accounts

    List every administrator and check creation dates since the plugin was installed. Remove accounts you do not recognise, including any that look temporary.

  4. Review Web Server Logs

    We recommend searching access logs for requests whose parameters contain usfw_, the prefix in the function name from the record title. The record does not say how the action is reached.

  5. Treat an Unknown Administrator as a Compromise

    Rotate administrator passwords, API keys and salts, end all sessions, and review installed plugins, theme files and scheduled tasks for changes.

Questions

Which Security For WooCommerce versions does CVE-2026-100109 affect?

The CVE record lists 1.0.10 through 1.0.16. It names no versions before 1.0.10 and no fixed release.

Is there a patch for the Security For WooCommerce flaw?

WPScan lists no known fix as of 5 November 2026, and WordPress.org shows the plugin as closed since 13 October 2026. Removal is the safe step until a fix exists.

Does an attacker need a login to create an administrator?

No. The record says the action is available to unauthenticated visitors and the CVSS vector sets privileges required to None.

Is CVE-2026-100109 in the CISA KEV catalog?

Not in catalog version 2026.11.04. KEV status can change, so check the catalog again before you rely on this.

Why does WPScan classify it differently from the CVE record?

The CVE record uses CWE-862, Missing Authorization. WPScan's page lists CWE-269 for the privilege escalation outcome. Both describe the same entry.

In our research

  1. UpdraftCentral Keys Stolen: How the WordPress Backdoor Campaign Works October 2026

Sources

  1. CVE-2026-100109 Record CVE Program / WPScan CNA
  2. CVE-2026-100109 NVD
  3. Security For WooCommerce 1.0.10 - 1.0.16 - Unauthenticated Privilege Escalation via usfw_create_temporary_user WPScan
  4. Security For WooCommerce WordPress.org Plugin Directory
  5. Known Exploited Vulnerabilities Catalog CISA