External risk intelligence

Automation Web Platform WordPress Plugin Authentication Bypass

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-77264

The vulnerability affects a WordPress plugin designed for public-facing e-commerce websites. Authentication and login portals are typically exposed to the public internet to allow user access, making this functionality a common internet-facing surface.

Authentication Bypass

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

A critical vulnerability has been identified in a WordPress plugin used for managing notifications and one-time passwords in WooCommerce. This flaw allows unauthenticated attackers to potentially bypass login procedures and access any user account, including administrative ones, by knowing the target user's email address. The core issue involves the plugin inadvertently exposing a secret login token.

  • Bypasses user logins for WordPress sites.
  • Allows unauthorized access to any user account.
  • Confirm plugin relevance and identify exposure.

Attack Path

How an attacker could exploit the issue

An attacker can bypass authentication by sending a request to a publicly accessible function that mistakenly reveals a secret login token in its response. If the attacker knows a target user's email address, they can use this token to log in as that user, potentially gaining administrative privileges.

  • Requires knowledge of user's email.
  • Publicly accessible OTP request.
  • Full account takeover.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow unauthenticated attackers to bypass authentication and log in as any user on a WordPress site, provided they know the target user's email address. This is possible because a secret login token is exposed in the response to publicly accessible One-Time Password (OTP) requests, rather than being exclusively sent to the user's email.

  • Site user accounts could be compromised.
  • Attackers could exploit exposed OTP requests.
  • Unauthorized access to any user's account.

Operational Fix

Recommended remediation, mitigation, and detection steps

For this WordPress plugin vulnerability, the application owner or the WordPress administrator is likely responsible for remediation. The first practical step is to identify all instances of the affected plugin on your WordPress sites, determine their exposure, and confirm the accountable owner. Following this, a risk-based plan for remediation can be developed, which may involve coordination with the plugin vendor.

  • WordPress administrators own this issue.
  • Verify plugin exposure and reachability.
  • Plan vendor coordination or upgrade.

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 Automation Web Platform plugin for WordPress?

This software is an add-on for WooCommerce stores designed to streamline customer communication. It specifically manages automated notifications and enables one-time password (OTP) authentication, allowing customers to log in or verify their identity via email codes rather than traditional passwords.

What is the vulnerability in CVE-2026-77264?

This vulnerability is classified as CWE-640, or Weak Password Recovery Mechanism. Essentially, the plugin's code mistakenly returns a secret login token directly in the server's response during an OTP request, instead of keeping that token private and sending it only to the user's verified email address.

How does an attacker trigger this authentication bypass?

An attacker initiates the bypass by sending a request to the plugin's public OTP endpoint. If they provide a valid email address belonging to a registered user, the system responds by disclosing the secret login token. Simply visiting the site or browsing normally does not trigger the bug; it requires crafting a specific request to that exposed function.

Is my site at risk according to Halo Surface Signal?

Yes, because this plugin powers login portals for e-commerce, it is inherently internet-facing. Halo Surface Signal identifies this as a critical concern since these authentication features must remain accessible to the public internet for normal business operations, meaning there is no internal-only isolation for this flaw.

What should I do if I use this WordPress plugin?

Begin by auditing your environment to locate all active installations of this specific plugin. Once identified, verify if the plugin is exposed to the internet, coordinate with your technical team to restrict access, and monitor the vendor's official channels for a security update to patch the logic error.

References