Trust Payments Gateway ≤ 1.3.8: A WP_Error Stored as a User ID Becomes an Admin Login (CVE-2026-110811, CVSS 9.8)

Running Trust Payments Gateway for WooCommerce on your site? Check it against CVE-2026-110811 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Trust Payments Gateway for WooCommerce is in the affected range (≤ 1.3.8), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

Trust Payments Gateway ≤ 1.3.8: A WP_Error Stored as a User ID Becomes an Admin Login (CVE-2026-110811, CVSS 9.8)

A payment plugin stored an error object where a user ID belonged — and the thank-you page trusted it. That is CVE-2026-110811, an unauthenticated authentication bypass to administrator in Trust Payments Gateway for WooCommerce, disclosed November 18, 2026 and rated CVSS 9.8.

What Happened

When a customer checks out, the plugin's new_customer_account() function calls wp_create_user() and stores the raw return value in the order's tp_userid post meta — before the is_wp_error() guard is evaluated. When the chosen username already exists, wp_create_user() does not return a user ID at all: it returns a WP_Error object. That error object is what gets stored as the user ID. The add_customer_details_to_thankyou_page() callback subsequently acts on the stored value, and the result is an unauthenticated authentication bypass to administrator (CWE-287).

Am I Affected?

Any WooCommerce store running Trust Payments Gateway for WooCommerce at 1.3.8 or below. Check Plugins in wp-admin, or the plugin's public readme — or run the free check at preshipit.com/free-scan, which reads the version your site announces and flags 1.3.8 and below. A site that discloses no version is reported as unverified, never as vulnerable.

What To Do Now

  1. Update Trust Payments Gateway to the newest available release. This is the fix; everything below is triage while you wait.
  2. Audit recently created users and orders. The bypass creates or reuses accounts through the checkout path, so look for users created around orders you cannot tie to a real customer, and for administrator accounts whose creation you cannot explain.
  3. Force a password reset and session invalidation for privileged accounts if an affected version was public. An auth bypass leaves no failed-login trail — the absence of failed logins proves nothing.
  4. Review checkout logs for the thank-you flow if your gateway logs the tp_userid meta — error objects stored as user IDs are the signature to look for.

The Bigger Lesson

Check the error before you store the result. is_wp_error() after the write is not a guard — it is a comment on a decision already made. Any function whose failure mode returns an object of a different type than its success mode is a type-confusion bug waiting for a caller that stores first and checks later. If your code calls a function that can return an error object, the check belongs on the very next line, before the value touches storage, a session, or a cookie.

Related: Jupiter X Core: An X Login That Checks the Owner, Not the Visitor — the earlier unauthenticated auth bypass in this series, where a social-login handler verified the site operator's identity instead of the visitor's.

Check Trust Payments Gateway for WooCommerce on your own site — free.

Our free WordPress Plugin Vulnerability Checker pulls Trust Payments Gateway for WooCommerce's current version from wordpress.org and lists the vulnerabilities our scanner checks for — CVE-2026-110811 included. No scan, no account.

Open the free plugin checker →

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Running Trust Payments Gateway for WooCommerce on your site? Check it against CVE-2026-110811 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Trust Payments Gateway for WooCommerce is in the affected range (≤ 1.3.8), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report