CVE-2026-92161: FriendsOfFlarum oauth · Insufficient Verification of Data Authenticity
Affects FriendsOfFlarum oauthSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 2.0.0-beta.4 or 1.7.4 as a priority.
Data as of 7 Nov 2026, 23:24 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.0.0-beta.4, 1.7.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Upgrade oauth and friendsofflarum/oauth to 2.0.0-beta.4 or 1.7.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| FriendsOfFlarumoauth | Affected
| Fixed in
|
| FriendsOfFlarumoauth | Affected
| Fixed in
|
GitHubfriendsofflarum/oauthpkg:github/friendsofflarum/oauthOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade FriendsOfFlarum OAuth to version 1.7.4 or later, or to 2.0.0-beta.4 or later. These versions include the fix that properly verifies the email 'verified' field from Discord OAuth responses before trusting the email address. No other mitigation is necessary as the issue is resolved in these versions.
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.
References
- github.com/FriendsOfFlarum/oauth/security/advisories/GHSA-g7vj-c29h-3h5m (opens in a new tab)
- github.com/FriendsOfFlarum/oauth/commit/baca3466b3b7be51c70a7e0ba966901aefeb344a (opens in a new tab)
- github.com/FriendsOfFlarum/oauth/commit/bb4bf376832e6bb68c579715d2a4b5a92c4a2567 (opens in a new tab)
- github.com/FriendsOfFlarum/oauth/releases/tag/1.7.4 (opens in a new tab)
- github.com/FriendsOfFlarum/oauth/releases/tag/2.0.0-beta.4 (opens in a new tab)