OCTOBER 6, 2026
Live Feed
Back to database
Case File

CVE-2026-92161

CRITICAL · CVSS 9.8 EPSS 0.27% Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-09-25 · Last synced 2026-10-06

CyberRota Analysis

AI-Generated

The vulnerability affects the FriendsOfFlarum OAuth integration for Discord, allowing an unauthenticated attacker to link their Discord account to a Flarum user's account using an unverified email address, thereby gaining unauthorized access without the victim's interaction. This critical flaw can lead to the compromise of user accounts, including those of administrators, if the victim's email is not already associated with a Discord account. Organizations using affected versions should prioritize updating to versions 1.7.4 or 2.0.0-beta.4 to mitigate this risk.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

Detected Signals
exploit

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-92161
Severity
CRITICAL
CVSS
9.8
EPSS
0.27%
GitHub

Original NVD Description

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.