External risk intelligence

Trust Payments Gateway Authentication Bypass in WooCommerce Plugin.

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-110811

This vulnerability affects a WordPress plugin designed for payment processing, which is inherently a public-facing web application component. As an internet-accessible checkout and payment gateway, it is commonly deployed in publicly reachable web environments where the plugin functionality is exposed to end-users and potential attackers over the internet.

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 vulnerability has been identified in the Trust Payments Gateway for WooCommerce plugin, a component used for processing payments on WordPress websites. This issue could allow unauthorized individuals to gain administrative access to affected sites, potentially impacting site integrity and operations. The main concern is confirming relevance and exposure to our WordPress environments.

  • Unauthenticated attackers can gain admin access.
  • Affects customer payment processing on WordPress.
  • Confirm if this payment plugin is used.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker can bypass authentication by exploiting how the Trust Payments Gateway plugin handles new user creation during checkout. By carefully crafting a new username that collides with an existing user, the attacker can manipulate the system into incorrectly storing an error message. When this message is later processed, it leads to the attacker being authenticated as the site's administrator. This allows the attacker to gain full control of the website.

  • Publicly accessible checkout page required.
  • Triggered by completing a paid order.
  • Gain administrator access.

Live Threat

Current exploitation, exposure, and threat context

When the Trust Payments gateway is active and an attacker completes a paid order, they could potentially bypass authentication. This is because a username collision can lead to the authentication of user ID 1, the primary administrator.

  • Administrator account access.
  • Bypassing authentication during checkout.
  • Unauthorized site control.

Operational Fix

Recommended remediation, mitigation, and detection steps

Given the context, the WordPress site administrators, platform teams, and security operations teams are likely responsible for addressing this critical vulnerability. The initial practical step is to identify all WordPress instances using the Trust Payments Gateway for WooCommerce plugin, determine their exposure and criticality, and confirm the accountable owner for each. Following this, a risk-based remediation plan should be developed, considering vendor coordination and potential maintenance windows.

  • Own the WordPress platform and plugin.
  • Verify plugin reachability and criticality.
  • Plan remediation with vendor coordination.

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 Trust Payments Gateway for WooCommerce?

It is a WordPress plugin that enables websites to process customer payments through the Trust Payments platform. It integrates directly into the checkout flow, allowing users to complete transactions on an e-commerce site. Because it manages sensitive payment interactions, it is designed to run within the public-facing areas of a store to ensure customers can finalize their purchases.

How does CVE-2026-110811 create an authentication bypass?

The flaw falls under Improper Authentication (CWE-287). It occurs when the plugin fails to properly validate a new user creation step during checkout. When a username conflict happens, the software incorrectly processes an error object as a valid user ID. This results in the system mistakenly logging the user in with the credentials of the site's primary administrator, effectively bypassing the login process entirely.

What triggers this vulnerability during checkout?

An attacker must trigger the bug by completing a paid order while the Trust Payments gateway is active. By entering a username during the checkout process that already exists on the site, the attacker forces the system into the vulnerable code path. Simply visiting the site or browsing products without successfully completing the payment process does not initiate the flaw.

Is my site at risk according to Halo Surface Signal?

If you are running the Trust Payments Gateway, Halo Surface Signal flags this as a significant concern because the plugin functions as an internet-accessible checkout component. Since payment gateways are inherently designed to be reachable by the public to accept orders, any site using this plugin is directly exposed to the internet, making the site's checkout flow a potential entry point for unauthorized administrative access.

What should I do first to address this security issue?

Start by performing an inventory of your WordPress installations to confirm if the Trust Payments Gateway is currently active. Once identified, locate the team responsible for managing those specific sites. Because this vulnerability provides full control to an attacker, prioritize these instances for review and coordinate with the plugin vendor for available updates or guidance on disabling the affected component until it is secured.

References