GHSA-MQ44-HM5C-4X5H
Vulnerability from github – Published: 2026-11-18 15:34 – Updated: 2026-11-18 15:34The 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.
{
"affected": [],
"aliases": [
"CVE-2026-110811"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-18T14:17:26Z",
"severity": "CRITICAL"
},
"details": "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()` \u2014 including a `WP_Error` object returned on username collision \u2014 into the order\u0027s `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 \u2014 the bootstrap site administrator or, on multisite, a network super-admin \u2014 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.",
"id": "GHSA-mq44-hm5c-4x5h",
"modified": "2026-11-18T15:34:33Z",
"published": "2026-11-18T15:34:33Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-110811"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/trust-payments-gateway-3ds2/tags/1.3.8/classes/class-wc-tp-gateway.php#L1880"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/trust-payments-gateway-3ds2/tags/1.3.8/classes/class-wc-tp-gateway.php#L303"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/trust-payments-gateway-3ds2/tags/1.3.8/classes/class-wc-tp-gateway.php#L308"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/2f2d3fd0-f890-4a80-83ad-0212c1333980?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.