CVE-2026-110811
validatedZero produced an exploit or a check.GHSA-mq44-hm5c-4x5h ↗EUVD-2026-128838 ↗
description
Trust Payments Gateway for WooCommerce JavaScript Library versions through 1.3.8 are affected. When the gateway is enabled, an unauthenticated attacker able to complete a paid checkout could gain an authenticated session as the WordPress account with ID 1.
mitigation
Disable the Trust Payments Gateway for WooCommerce plugin or gateway until the vendor supplies a corrected release. No fixed version is recorded; review administrator sessions and accounts for unexpected activity.
outcome
Upstream: a detection for this already ships elsewhere, so we didn't generate a new one. The credit goes to whoever did.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-11-18 13:32Zcve_org: trigger signal, started the run
- 2026-11-18 13:46Z
this entry in the feed
GET /api/v1/feed/CVE-2026-110811
{ "etk_id": "ETK-2026-4802", "cve_id": "CVE-2026-110811", "display_id": "CVE-2026-110811", "ghsa_id": "GHSA-mq44-hm5c-4x5h", "euvd_id": "EUVD-2026-128838", "status": "published", "anchor_state": "anchored", "title": "Authentication bypass in Trust Payments Gateway for WooCommerce", "summary": "Trust Payments Gateway for WooCommerce JavaScript Library versions through 1.3.8 are affected. When the gateway is enabled, an unauthenticated attacker able to complete a paid checkout could gain an authenticated session as the WordPress account with ID 1.", "mitigation": "Disable the Trust Payments Gateway for WooCommerce plugin or gateway until the vendor supplies a corrected release. No fixed version is recorded; review administrator sessions and accounts for unexpected activity.", "vendor": "trustpayments", "product": "Trust Payments Gateway for WooCommerce (JavaScript Library)", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 0, <= 1.3.8" ], "ecosystem": null, "fixed_versions": [], "package_name": "Trust Payments Gateway for WooCommerce (JavaScript Library)", "purl": null } ], "cwes": [ 287 ], "cvss_score": 9.8, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "deterministic", "check": true, "check_confidence_basis": "upstream", "exploit": false, "pipeline_minutes": 0.2098844, "t0_at": "2026-11-18T13:32:22.538000+00:00", "signals": { "check": { "at": "2026-11-18T13:46:16.213042+00:00", "days": 0.009649016689814814, "is_lower_bound": false, "measured_at": "2026-11-18T13:32:22.538000+00:00", "url": null }, "trigger_signal": { "at": "2026-11-18T13:32:22.538000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-11-18T13:32:22.538000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-110811" } } }
published 2026-11-18 13:46Z
last change 2026-11-18 21:43Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.