Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-92161 critical CVSS 9.8

Vulnerability in fof/oauth (CVE-2026-92161)

Summary

Vulnerability in fof/oauth (CVE-2026-92161). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.0.0-beta.4 or later.

Original description

The description as published by the source.

Impact

An unauthenticated account takeover vulnerability exists in fof/oauth when the Discord OAuth provider is enabled.

Discord allows an account to use an unverified email address when its phone number has been verified. During OAuth authentication, Discord may return that email address with "verified": false.

Affected versions of fof/oauth did not validate this flag and passed the email address to Flarum core as trusted via provideTrustedEmail(). Flarum core could then match the trusted email address to an existing user, link the attacker-controlled Discord identity to that user, and authenticate the attacker as the victim.

An attacker who knows a user's email address can therefore take over the corresponding Flarum account without knowing its password or requiring any interaction from the victim. This includes administrator accounts.

Preconditions for exploitation

  1. Discord sign-in is enabled on the forum.
  2. The victim has a Flarum account with a known email address.
  3. The victim's email address is not already associated with a Discord account.
  4. The attacker creates or configures a Discord account using the victim's email address without verifying it and verifies a phone number instead.
  5. The attacker authenticates to the forum using that Discord account.

The issue is specific to Discord's ability to return an unverified email address through OAuth. Other bundled providers were not confirmed to be practically exploitable through the same meth…

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-92161 has been found in fof/oauth.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade fof/oauth to 2.0.0-beta.4 or later.
If unsure, ask your IT team or search "fof/oauth CVE-2026-92161" on the vendor's site.

CVE-2026-92161 (fof/oauth) — CWE-345 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.0.0-beta.4 — apply immediately
Workaround: Administrators who cannot update immediately should disable the Discord OAuth provider in the extension settings.
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

A vulnerability (CWE-345) exists in fof/oauth.

📍 Affected scope

Check the vendor advisory for the affected versions of fof/oauth.

🔥 Severity

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

🔧 How to fix

Update to 2.0.0-beta.4.

🛡️ Workaround

Workaround: Administrators who cannot update immediately should disable the Discord OAuth provider in the extension settings.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'fof/oauth' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

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

  1. 1
    Identify exposure identify 
    grep -r 'fof/oauth' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で fof/oauth を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    Administrators who cannot update immediately should disable the Discord OAuth provider in the extension settings.

    パッチが適用されるまでの応急処置として、Administrators who cannot update immediately should disable the Discord OAuth provider in the extension settings. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade fof/oauth to 2.0.0-beta.4

    ステージング環境で 2.0.0-beta.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

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

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

Affected packages

composer fof/oauth
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.0-beta.4"}]}]

References

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