CVE-2026-110811: Trust Payments Gateway for WooCommerce (JavaScript Library) <= 1.3.8 - Unauthenticated Authentication Bypass to Administrator via Guest-Registration WP_Error Coercion

Published Nov 18, 2026
·
Updated

The Trust Payments Gateway for WooCommerce (JavaScript Library) plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 1.3.8. The vulnerability exists because the newcustomeraccount() function stores the raw return value of wpcreateuser() — including a WPError object returned on username collision — into the order's tpuserid post meta before the iswperror() guard is evaluated; the addcustomerdetailstothankyoupage() callback subsequently reads that meta and casts it with (int), causing PHP to coerce any object to integer 1, after which wpsetcurrentuser(1) and wpsetauthcookie(1) are called unconditionally. This makes it possible for unauthenticated attackers to authenticate as WordPress user ID 1 — the bootstrap site administrator or, on multisite, a network super-admin — by supplying the newusername parameter matching any existing login during checkout and visiting the resulting thank-you page. Exploitation requires the Trust Payments gateway to be active and the attacker to complete a paid order on their own account; the ID 1 administrator username is additionally enumerable via standard WordPress user enumeration techniques.

Affected Software

1 affected component
Trust Payments Trust Payments Gateway for WooCommerce (JavaScript Library)<=1.3.8

Event History

Nov 18, 2026
CVE Published
via MITRE·01:32 PM
Data Sourced
via MITRE·01:32 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What conditions must be met for exploitation?

The Trust Payments gateway must be active. An unauthenticated attacker must complete a paid order using their own account, submit a new_username value that matches an existing WordPress login, and visit the resulting thank-you page.

2

Which account can an attacker obtain through this issue?

The vulnerable callback coerces the stored WP_Error object to user ID 1 and unconditionally sets that user's authentication cookie. On a typical site, ID 1 is the bootstrap site administrator; on multisite, it may be a network super-admin.

3

Does the attacker need to know the administrator username?

The supplied username only needs to match any existing WordPress login to make wp_create_user() return an error. The description also notes that the ID 1 administrator username is enumerable through standard WordPress behavior, but the bypass itself authenticates the attacker as user ID 1.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203