Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-104759 high CVSS 8.1

Authentication Bypass in WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WordPress plugin) (CVE-2026-104759)

Summary

Authentication bypass in WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WordPress plugin) (CVE-2026-104759). Successful exploitation can lead to full system takeover. Exploitable via id_token.

Original description

The description as published by the source.

The WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) plugin for WordPress is vulnerable to Authentication Bypass via OIDC Nonce Replay in all versions up to, and including, 44.1 This is due to Id_Token_Service_Deprecated::process_openidconnect_token() using the incompatible WordPress core wp_verify_nonce() function to validate a nonce produced by Nonce_Service::create_nonce() — a 64-character hex value that wp_verify_nonce() can never successfully verify — causing the nonce check to silently fail without terminating authentication, so execution continues into authenticate_oidc_user() with the attacker-supplied id_token. This makes it possible for unauthenticated attackers who have obtained a previously-issued, valid id_token for a target account to replay that token and authenticate as any WordPress user, including administrators, resulting in full site takeover. This vulnerability is only exploitable when the use_id_token_parser_v2 plugin option is enabled, as this is the configuration that routes token processing through the deprecated parser containing the broken nonce check.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-104759 has been found in WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WordPress plugin).
Attackers can target a specific entry point like id_token over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WordPress plugin) CVE-2026-104759" on the vendor's site.

CVE-2026-104759 (WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WordPress plugin)) — CWE-287 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: id_token / use_id_token_parser_v2
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Authentication bypass (CWE-287) exists in WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WordPress plugin). Attackers reach the vulnerable code path via id_token without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WordPress plugin). Attack surface: id_token / use_id_token_parser_v2.

🔥 Severity

Severity: High (CVSS 8.1/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WordPress plugin) を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details