CVE-2026-110811: Trust Payments Gateway for WooCommerce (JavaScript Library) (WordPress plugin) · Improper Authentication
Affects Trust Payments Gateway for WooCommerce (JavaScript Library) (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 18 Nov 2026, 13:49 UTC
Thin evidence
One scorer or none| CNA (Wordfence) | CVSS 3.1 | 9.8 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| trustpaymentsTrust Payments Gateway for WooCommerce (JavaScript Library) | Affected
| Fixed in– |
Description
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 `new_customer_account()` function stores the raw return value of `wp_create_user()` — including a `WP_Error` object returned on username collision — into the order's `tp_userid` post meta before the `is_wp_error()` guard is evaluated; the `add_customer_details_to_thankyou_page()` callback subsequently reads that meta and casts it with `(int)`, causing PHP to coerce any object to integer `1`, after which `wp_set_current_user(1)` and `wp_set_auth_cookie(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 `new_username` 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.
References
- wordfence.com/threat-intel/vulnerabilities/id/2f2d3fd0-f890-4a80-83ad-0212c1333980?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/trust-payments-gateway-3ds2/tags/1.3.8/classes/class-wc-tp-gateway.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/trust-payments-gateway-3ds2/tags/1.3.8/classes/class-wc-tp-gateway.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/trust-payments-gateway-3ds2/tags/1.3.8/classes/class-wc-tp-gateway.php (opens in a new tab)