On this page (7 sections)
A critical flaw tracked as CVE-2026-110811 affects the Trust Payments Gateway for WooCommerce (JavaScript Library) plugin for WordPress in all versions up to and including 1.3.8. According to the GitHub Advisory Database entry, an unauthenticated attacker can end up logged in as WordPress user ID 1, which is normally the first administrator account.
If you run a WooCommerce store that accepts payments through this gateway, treat this as urgent. The advisory lists no patched version, so you may need to disable the gateway rather than wait for an update.
What happened
The vulnerability was published on November 18, 2026 to the National Vulnerability Database and the GitHub Advisory Database. The description says the plugin mishandles the result of a user-creation call during checkout, and that this can be abused to obtain an authenticated session as user ID 1.
The GitHub entry is marked as unreviewed, lists no package, and shows affected and patched versions as unknown. The NVD record repeats the same description, so it is not independent confirmation. The advisory also links to a Wordfence entry. Only one independent publisher covers this story so far, and no vendor statement or fix was available in the research.
Technical details in plain terms
The advisory describes a type-handling mistake. When a customer places an order, the plugin's new_customer_account() function creates a WordPress user and saves the return value in the order's tp_userid metadata. If the chosen username already exists, WordPress returns an error object instead of a user ID. The plugin saves that error object before checking whether it is an error.
Later, on the order thank-you page, another function reads that stored value and casts it to an integer. In PHP, an object cast this way becomes 1. The plugin then calls wp_set_current_user(1) and wp_set_auth_cookie(1) without further checks, which signs the visitor in as user ID 1.
This is a classic improper authentication problem: the code trusts a value that was never validated as a real, newly created account. Per the advisory, the attacker supplies a new_username parameter that matches any existing login during checkout, then visits the resulting thank-you page.
What limits the attack
- The Trust Payments gateway must be active on the site.
- The attacker must complete a paid order on their own account, so it is not completely free to try.
- The administrator account with ID 1 can often be discovered with standard WordPress user enumeration, according to the advisory.
These conditions narrow the attack but do not make it difficult. The CVSS vector rates complexity as low and requires no privileges and no user interaction.
Who is affected
Any WordPress site running version 1.3.8 or earlier of this plugin with the gateway enabled at checkout is in scope. On multisite installs, the advisory says user ID 1 is a network super-admin, which raises the impact further.
A successful login as an administrator can mean control over the whole site: installing plugins, editing code, creating other admins, and reading order and customer data. The advisory does not describe what attackers have done in practice, and no exploitation has been reported in the sources reviewed.
How to check your exposure
First, find out whether the plugin is installed, which version it is, and whether it is active. This WP-CLI command lists plugins with their status and version. Run it from the site's root directory and look for an entry related to Trust Payments.
wp plugin list --fields=name,status,versionThe plugin's directory on WordPress.org appears to use the slug trust-payments-gateway-3ds2, based on the source links in the advisory. If your list shows that plugin at 1.3.8 or lower with status active, you are exposed.
Next, see which account has ID 1 and whether it is an administrator. This read-only command lists the user with that ID.
wp user list --include=1 --fields=ID,user_login,roles,user_registeredWhat to do now
- Confirm whether the Trust Payments Gateway plugin is installed and active, and note its version.
- If it is active and at 1.3.8 or lower, disable the gateway in WooCommerce payment settings or deactivate the plugin until the vendor publishes a fixed version.
- Check the plugin's page on WordPress.org and the vendor's channels for an update, since the advisory lists no patched version. Do not assume a newer version is safe until its release notes mention this issue.
- Review the administrator accounts under Users in the dashboard. Remove any you do not recognize and check recent changes to roles.
- Reset passwords for administrators and force a logout of all sessions, particularly if the gateway was active at any point after the advisory became public.
- Review recent orders for suspicious patterns, such as paid orders where the customer-supplied username matches an existing admin login.
- Make sure you have a recent, tested backup before you change anything, and keep it stored off the server.
Detection and monitoring
Because the sources report no confirmed exploitation, you cannot assume your site was or was not targeted. Look for signs of an unexpected administrator session instead.
- Admin logins at times when no one on your team was working, especially for the ID 1 account.
- New administrator users, new or changed plugins, or edited theme and plugin files.
- Orders that completed shortly before an unexplained admin login from the same IP address.
- Web server log entries for checkout and order-received requests that include an unusual new_username value.
To search your access logs for requests containing that parameter, you can use a read-only grep. Adjust the log path for your server; the path below is a common Debian/Ubuntu Apache location and may differ on your host. Many matches are not proof of an attack, since legitimate customers may also submit that field, so review the results alongside order and login records.
grep -i "new_username" /var/log/apache2/access.logNote that checkout data is often sent in POST bodies, which standard access logs do not record, so an empty result does not rule out abuse. For ongoing visibility, Webforta Monitor can watch uptime, certificates, DNS and header changes, and the free malware scanner can help spot visible signs of compromise. Neither is a substitute for removing the vulnerable plugin. See also our guides on checking whether a website is hacked and what to do after a hack.
What we do not know yet
- No fixed version is named in the advisory, and the patched versions field is listed as unknown.
- The GitHub entry is unreviewed and lists no package.
- The sources do not report active exploitation, and there is no CISA KEV listing in the research.
- There is no vendor advisory in the research. Details come from the CVE description, which links to the plugin's version 1.3.8 source code and a Wordfence entry.
We will not claim more than the sources show. Check the plugin's official page and the linked Wordfence entry for updates. For broader hardening of a store, see our WordPress security checklist and security for online stores.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
