CVE-2026-110811: Trust Payments Gateway for WooCommerce (JavaScript Library) <= 1.3.8 - Unauthenticated Authentication Bypass to Administrator via Guest-Registration WP_Error Coercion
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
Event History
Frequently Asked Questions
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.
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.
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.