External risk intelligence

Security For WooCommerce Plugin User Token Generation Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-123695

The vulnerability affects a WordPress plugin, which is a web application component commonly deployed as an internet-facing service. The flaw exists within REST API routes that are accessible to the public, making the attack surface readily reachable in standard web deployments.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This critical vulnerability impacts a widely used WordPress plugin, enabling unauthenticated attackers to generate login tokens for any user, including administrators, and gain unauthorized access to accounts. This could allow for extensive compromise of online store data and operations.

  • Unauthorized account access is possible.
  • Confirms exposure of customer and administrative data.
  • Ensure plugin relevance and scan for impact.

Attack Path

How an attacker could exploit the issue

An attacker could access the plugin's REST API without logging in, then use this access to create login tokens for any user. With these tokens, the attacker can then log in as any user, including administrators, to gain full control of the site.

  • Unauthenticated access to API routes.
  • Generate and retrieve user login tokens.
  • Full site control, including admin access.

Live Threat

Current exploitation, exposure, and threat context

The Security For WooCommerce WordPress plugin could allow unauthenticated users to generate and retrieve login tokens for any user. When supported, this could enable an attacker to log in as any user, including administrators, by exploiting unprotected REST API routes.

  • User account access and data.
  • Unprotected API routes allow token generation.
  • Unauthorized access to user accounts.

Operational Fix

Recommended remediation, mitigation, and detection steps

Understanding the reach and criticality of the Security For WooCommerce plugin is the first step. This vulnerability allows unauthenticated users to generate and retrieve login tokens for any user, including administrators, by exploiting unrestricted REST API routes. This means that the application owner or platform team responsible for the WooCommerce deployment needs to identify all instances of this plugin, assess their exposure and business impact, and then coordinate remediation efforts with the vendor or an internal security team.

  • Application owners should own the issue.
  • Verify plugin reachability and business criticality.
  • Plan coordinated remediation with the vendor.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Security For WooCommerce plugin?

It is a WordPress extension designed to manage and protect e-commerce store functions. Users install it to enhance the security of their online shops built on the WooCommerce platform, which handles sensitive customer data and store settings.

What does CWE-269 mean for CVE-2026-123695?

This vulnerability falls under Improper Privilege Management. In simple terms, the plugin fails to verify who is allowed to perform certain sensitive actions. Because of this, the system mistakenly grants unauthenticated users the ability to perform high-level tasks reserved for legitimate users.

How does an attacker trigger this vulnerability?

An attacker targets specific REST API routes within the plugin that were left without access restrictions. They do not need to be logged in to send requests to these endpoints. Simply sending a crafted request triggers the API to generate a valid login token for any user on the system. Normal user interaction, such as simply browsing the site, does not trigger this flaw.

Why should I be concerned about this CVE?

Halo Surface Signal notes that since this is a WordPress plugin, it is typically used in internet-facing web applications. This means the affected API routes are likely reachable from the public web, allowing attackers to access the site remotely without any specialized internal network access.

Do I need to take action if I use this plugin?

Yes. First, locate all websites where the Security For WooCommerce plugin is installed to understand your footprint. Assess the business risk of your installations, then coordinate with your technical team or the vendor to apply necessary updates or mitigation steps to block unauthorized API access.

References