CVE-2026-104759
waiting for further signalsZero needs more public information before it can validate it.GHSA-p38j-g4g4-fm3g ↗EUVD-2026-96286 ↗
description
WPO365 Login versions through 44.1 can accept replayed OpenID Connect ID tokens when the deprecated v2 ID-token parser is enabled. An unauthenticated attacker with a previously issued valid token for an account may sign in as that account, including an administrator.
mitigation
Disable the use_id_token_parser_v2 option immediately to avoid the affected token-processing path. Monitor for and apply a vendor release that fixes the issue; no fixed version is recorded in the advisory.
outcome
Contextual: an exploit technique exists, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-10 07:41Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-104759
{ "etk_id": "ETK-2026-1158", "cve_id": "CVE-2026-104759", "display_id": "CVE-2026-104759", "ghsa_id": "GHSA-p38j-g4g4-fm3g", "euvd_id": "EUVD-2026-96286", "status": "published", "anchor_state": "anchored", "title": "OIDC token replay authentication bypass in WPO365 Login", "summary": "WPO365 Login versions through 44.1 can accept replayed OpenID Connect ID tokens when the deprecated v2 ID-token parser is enabled. An unauthenticated attacker with a previously issued valid token for an account may sign in as that account, including an administrator.", "mitigation": "Disable the use_id_token_parser_v2 option immediately to avoid the affected token-processing path. Monitor for and apply a vendor release that fixes the issue; no fixed version is recorded in the advisory.", "vendor": "wpo365", "product": "WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN)", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 0, <= 44.1" ], "ecosystem": null, "fixed_versions": [], "package_name": "WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN)", "purl": null } ], "cwes": [ 287 ], "cvss_score": 8.1, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H", "epss_score": 0.0052, "epss_percentile": 0.4269, "epss_asof": "2026-10-20", "automation": "contextual", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 48.47773393333333, "t0_at": "2026-10-10T07:41:47.371000+00:00", "signals": { "trigger_signal": { "at": "2026-10-10T07:41:47.371000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-10T07:41:47.371000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-104759" } } }
published 2026-10-10 10:56Z
last change 2026-10-21 04:45Z
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.