Vulnerability DatabaseCVE-2026-100109

CVE-2026-100109: 
WordPress vulnerability analysis and mitigation

Overview

CVE-2026-100109 is a critical unauthenticated privilege escalation vulnerability in the Security For WooCommerce WordPress plugin (slug: ultimate-security-for-woocommerce), affecting versions 1.0.10 through 1.0.16. The plugin fails to perform capability checks on the usfw_create_temporary_user AJAX action, which is accessible to unauthenticated visitors, and allows the caller to freely specify the new account's role — including administrator. This enables a remote, unauthenticated attacker to create an administrator account and fully take over the WordPress site. It was publicly disclosed on November 3–5, 2026, with a CVSS v3.0 base score of 9.8 (Critical) (GitHub Advisory, WPScan).

Technical details

The root cause is CWE-862 (Missing Authorization): the plugin registers the usfw_create_temporary_user action as a nopriv WordPress AJAX handler, meaning it is reachable without authentication, and it performs no capability or role validation before creating the new user account (GitHub Advisory, WPScan). An attacker first harvests a valid plugin-issued AJAX nonce from any public page of the site (e.g., homepage, shop, checkout), then sends a crafted HTTP POST to admin-ajax.php with action=usfw_create_temporary_user, the harvested nonce, an attacker-controlled email address, and role=administrator. Because no server-side authorization check exists, WordPress creates the account at the requested privilege level. The attacker then triggers a standard WordPress password reset to the attacker-controlled email to obtain credentials. A public Python PoC (poc.py) automating this full chain is available on GitHub (PoC Repo).

Impact

Successful exploitation grants the attacker a fully privileged WordPress administrator account, resulting in complete confidentiality, integrity, and availability compromise of the affected site. With administrator access, an attacker can install malicious plugins or themes, inject backdoors, exfiltrate all site data (including customer PII and payment-related information stored by WooCommerce), deface the site, or use the server as a pivot point for further attacks against the hosting environment (WPScan, GitHub Advisory). The attack requires no prior authentication or user interaction, making mass exploitation straightforward and automatable.

Exploitability

A functional, high-confidence Python proof-of-concept exploit (poc.py) was published on GitHub on November 6, 2026, one day after the CVE was disclosed, automating the full attack chain from nonce extraction to administrator account creation and password reset (PoC Repo). The EPSS score is approximately 0.369% (31st percentile), and as of the time of reporting, no confirmed in-the-wild exploitation has been observed and the CVE is not listed in the CISA KEV catalog (GitHub Advisory). The vulnerability is rated automatable by NVD SSVC analysis, meaning it can be exploited at scale without manual interaction. No specific threat actor attribution has been reported.

Exploitation steps

  1. Reconnaissance: Identify WordPress sites running the ultimate-security-for-woocommerce plugin in versions 1.0.10–1.0.16 using tools like WPScan, Shodan, or by checking plugin metadata at wp-content/plugins/ultimate-security-for-woocommerce/.
  2. Nonce Harvesting: Send HTTP GET requests to public pages of the target site (e.g., homepage, /shop/, /checkout/, /wp-login.php) and regex-match the plugin's JavaScript object var ultimate_security_for_woocommerce_ajax_obj = {...} to extract the AJAX nonce and ajax_url values.
  3. Unauthenticated Admin Account Creation: Send an HTTP POST to admin-ajax.php with the parameters action=usfw_create_temporary_user, security=<harvested_nonce>, email=<attacker@attacker.com>, user_name=<random>, and role=administrator. The server creates the account without any authorization check.
  4. Verify Success: Parse the JSON response from the server; a success: true value confirms the administrator account was created. On failure, the data.error_message field provides diagnostic information.
  5. Password Reset Takeover: POST to wp-login.php?action=lostpassword with user_login=<attacker@attacker.com> to trigger a WordPress password reset email to the attacker-controlled mailbox.
  6. Site Takeover: Open the password reset link received in the attacker's email, set a new password, and log in to /wp-admin with full administrator privileges to complete the takeover (PoC Repo).

Indicators of compromise

  • Network: Unusual HTTP POST requests to admin-ajax.php with action=usfw_create_temporary_user from unknown or unexpected IP addresses; POST requests to wp-login.php?action=lostpassword shortly after the above, especially for newly created accounts.
  • Logs: WordPress access logs showing repeated GET requests to public pages (homepage, /shop/, /checkout/) followed immediately by POST to admin-ajax.php from the same IP; entries in WordPress authentication logs for new administrator account creation.
  • WordPress Admin: Unexpected new administrator accounts in the WordPress user list, particularly accounts with auto-generated usernames (e.g., poc followed by a hex string) or unfamiliar email addresses; review wp_users and wp_usermeta tables for recently created users with wp_capabilities set to administrator.
  • File System: New or modified plugin/theme files, web shells, or backdoors installed after the account creation event, indicating post-exploitation activity.

Mitigation and workarounds

WPScan reports no known fix is currently available for the ultimate-security-for-woocommerce plugin as of the disclosure date; the affected version range is 1.0.10 through 1.0.16 (WPScan). As an immediate workaround, disable or uninstall the plugin until a patched version is released by the vendor. Administrators should audit their WordPress user tables for unauthorized administrator accounts created during any potential exposure window and remove them immediately. Additionally, restrict access to admin-ajax.php at the web server or WAF level where operationally feasible, and monitor for the IOCs described above.

Community reactions

The vulnerability was noted in Wordfence's weekly WordPress vulnerability report for November 2–8, 2026, highlighting it as a critical unauthenticated privilege escalation issue (Wordfence Blog). The CVE was also discussed on Mastodon/Infosec.exchange and Bluesky shortly after disclosure, and was picked up by automated vulnerability tracking services including VulDB, Vulners, and CIRCL. The original researcher credited is "Afan" via WPScan's responsible disclosure program (WPScan).

Additional resources


Source: This report was generated using AI

Related WordPress vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-125294CRITICAL9.8
  • the-plus-addons-for-block-editor-pro
NoYesNov 21, 2026
CVE-2026-130323HIGH7.2
  • stripe-payments
NoYesNov 21, 2026
CVE-2026-124976HIGH7.2
  • swift-performance-lite
NoYesNov 21, 2026
CVE-2026-126705MEDIUM6.5
  • wp-job-portal
NoYesNov 21, 2026
CVE-2026-124248MEDIUM5.4
  • gptranslate
NoYesNov 21, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management