Back to feed
21Track

trustpayments Trust Payments Gateway for WooCommerce (JavaScript Library): Authentication bypass

trustpayments Trust Payments Gateway for WooCommerce (JavaScript Library) · CVE-2026-110811 ETK-2026-4802 EUVD-2026-128838 GHSA-MQ44-HM5C-4X5H
0 news outlets0 CERTs and agencies1 research labs

Assessment: Track

SSVC decision points: exploitation none, automatable yes, technical impact total, deployment low.

What is it?

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

Evidence

Technical advisories1Detailed write-ups from security research teams

Exploitation

  • Exploit code published (not verified by us)
  • Exploited in the wild (confirmed by a source)
  • Listed as known exploited (CISA KEV)
CVSS
9.8
EPSS
–
First seen
14 h ago
Status
confirmed

All trustpayments vulnerabilities