CVE Catalog

CVE-2026-92161

CriticalCVSS 9.8
Published: Translated: NVD NIST

Summary

Before versions 1.7.4 and 2.0.0-beta.4, the Discord OAuth provider in FriendsOfFlarum does not check the 'verified' field for an OAuth email before passing it to Flarum core as trusted. This allows an unauthenticated attacker who knows a victim's email address to configure a Discord account with that unverified address and sign in as the victim without a password.

Risk Assessment

The attack can lead to compromise of administrator accounts and unauthorized access to user data in Flarum.

Recommendation

Update FriendsOfFlarum to version 1.7.4 or 2.0.0-beta.4, which contain the fix.

Related vulnerabilities

Original NVD description (English source)

FriendsOfFlarum OAuth allows users to log in to Flarum with GitHub, Twitter, Facebook, and other providers. Prior to 1.7.4 and 2.0.0-beta.4, the Discord OAuth provider does not check the verified field returned for an OAuth email before passing the address to Flarum core as trusted through provideTrustedEmail(). When Discord sign-in is enabled, an unauthenticated attacker who knows the email address of a Flarum user can configure a Discord account with that unverified address and a verified phone number, then sign in to cause Flarum to match the trusted address, link the attacker-controlled Discord identity to the existing user, and authenticate as the victim without a password or victim interaction. Exploitation requires that the victim's email address is not already associated with a Discord account, and it can compromise administrator accounts. Other bundled providers were not confirmed to be practically exploitable by this method because their relevant authentication flows return only verified or confirmed email addresses. This issue is fixed in versions 1.7.4 and 2.0.0-beta.4.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS