CVE
Trust Payments Gateway for WooCommerce authentication bypass in checkout account creation
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
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.
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.8, total technical impact per CISA
- No patch5/5No patch listed yet
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 40 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-110811 (Trust Payments Gateway for WooCommerce (JavaScript Library) <= 1.3.8 - Unauthenticated Authentication Bypass to Administrator via…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-110811 (entry last updated 2026-11-18):
Affected:
- trustpayments Trust Payments Gateway for WooCommerce (JavaScript Library): through 1.3.8
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-110811 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-110811 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/2f2d3fd0-f890-4a80-83ad-0212c1333980?source=cve
- https://plugins.trac.wordpress.org/browser/trust-payments-gateway-3ds2/tags/1.3.8/classes/class-wc-tp-gateway.php#L303
- https://plugins.trac.wordpress.org/browser/trust-payments-gateway-3ds2/tags/1.3.8/classes/class-wc-tp-gateway.php#L1880
- https://plugins.trac.wordpress.org/browser/trust-payments-gateway-3ds2/tags/1.3.8/classes/class-wc-tp-gateway.php#L308
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-110811
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-110811"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
- Posted on X by cve.now
Affected versions
- trustpayments Trust Payments Gateway for WooCommerce (JavaScript Library)
through 1.3.8
Evidence 6
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-110811
Is CVE-2026-110811 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-110811?
Trust Payments Gateway for WooCommerce (JavaScript Library): through 1.3.8.Source: cve.now feed data