Chargebacks & Fraud

Two WooCommerce Add-Ons Let Strangers Become Store Administrators

Registration Form for WooCommerce through 1.1.4 and Security For WooCommerce through 1.0.16 both let unauthenticated visitors gain administrator access. ThemeGrill fixed its plugin in 1.1.5 on November 6, 2026; Security For WooCommerce has no known fix and is closed on WordPress.org.

In a store back room as the November sun sets, a shopkeeper studies a list on his computer while a co-worker holding a ring of keys points at the screen, the kind of account check WooCommerce stores now need after two plugin flaws handed out administrator access.

Two WordPress plugins made for WooCommerce stores contain critical flaws that let a visitor with no account take control of a site as an administrator. ThemeGrill fixed its Registration Form for WooCommerce plugin in version 1.1.5, released November 6, 2026. The second plugin, Security For WooCommerce, has no known fix, and WordPress.org has not offered it for download since October 13.

Both flaws carry a severity score of 9.8 out of 10 under the Common Vulnerability Scoring System (CVSS), and neither requires the attacker to log in first.

A role field the checkout never checked

The Registration Form for WooCommerce bug, tracked as CVE-2026-119075, affects every version through 1.1.4. According to the Wordfence advisory published November 6, the plugin compared a submitted user role against the form’s allowed roles when shoppers registered on the My Account page, but skipped that comparison when an account was created during checkout. An attacker who added user_roles=administrator to a checkout registration would get a new account with full Administrator rights.

Wordfence credits researcher JB Sabit with the report. The plugin’s WordPress.org listing shows more than 1,000 active installations, and its changelog describes the 1.1.5 release as a fix that “prevented privilege escalation via the user role submitted at checkout.” Version 1.1.4, which shipped two days earlier on November 4, is still vulnerable.

Login tokens handed out over open REST routes

The Security For WooCommerce flaw, CVE-2026-123695, works differently. The WPScan advisory, first published November 9, says versions through 1.0.16 leave several of the plugin’s REST API routes open to anyone. An unauthenticated visitor can ask the plugin to generate login tokens for every user on the site, read those tokens back and sign in as any of them, administrators included. The National Vulnerability Database entry went live November 11.

WPScan, which credits researcher Aabideen Bangash, listed “No known fix” when it last updated the entry on November 16. It plans to publish a proof of concept on December 9. The plugin’s WordPress.org page says it “has been closed as of October 13, 2026 and is not available for download,” a closure WordPress.org describes as temporary while a full review takes place.

That closure matters for anyone who still has the plugin installed. A closed plugin does not push updates through the WordPress dashboard, so a store running Security For WooCommerce will not see an update notice to tell it something is wrong. A few third-party vulnerability summaries advise upgrading to version 1.0.17, but neither WPScan nor WordPress.org lists such a release. Until a fixed version appears, the open routes stay available on any site that keeps the plugin active.

What an administrator account can reach

On a WooCommerce site, the Administrator role can install plugins, edit theme files, change payment gateway settings and export customer and order data. That is the access an attacker needs to add a card skimmer to checkout or swap a store’s gateway credentials, the kind of tampering that can end in a data compromise investigation and hard questions from a high-risk merchant’s processor. EC4IM covered a related pattern on another platform in Hijacked Shopify App Settings Sent Shoppers to Fake Payment Pages Before Checkout.

Installing a fix closes the hole but does not remove an account an attacker already created. The security news site DaySec recommends confirming the installed version after updating, testing a normal customer registration and checkout, and reviewing Administrator accounts for recent additions that do not match approved staff. If an unfamiliar administrator turns up, DaySec advises keeping the registration and access records and investigating that account’s activity rather than treating the update as the cleanup.

Checks merchants can run this week

  • Find the plugins. In the WordPress Plugins screen, look for Registration Form for WooCommerce by ThemeGrill and for Security For WooCommerce (slug ultimate-security-for-woocommerce).
  • Confirm the version. Registration Form for WooCommerce should read 1.1.5 or later. Security For WooCommerce has no listed fixed version.
  • Review administrators. Filter the Users screen by the Administrator role and compare every account, and its registration date, against the people who should have that access.
  • Check payment settings. Compare gateway API keys and checkout settings against what the processor issued. EC4IM’s guide to rotating Authorize.Net transaction and signature keys after a WordPress compromise walks through one gateway’s process.

One patched, one still open

ThemeGrill’s 1.1.5 release closes the checkout role flaw in Registration Form for WooCommerce, though stores that ran 1.1.4 or earlier still need to confirm no administrator slipped in before they updated. Security For WooCommerce is the harder case. Its token flaw has no known fix, WordPress.org has pulled the plugin pending review, and WPScan’s proof of concept is scheduled for December 9, which leaves stores still running it with a short window to decide what to do.

Sources