Skip to main content
VulnerabilityPublished Updated

CVE-2026-92161: FriendsOfFlarum oauth · Insufficient Verification of Data Authenticity

Affects FriendsOfFlarum oauthSource CVE Database V5

0
Compare

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

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
FriendsOfFlarumoauthAffected
  • >=2.0.0-beta.1 <2.0.0-beta.4
Fixed in
  • 2.0.0-beta.4
FriendsOfFlarumoauthAffected
  • <1.7.4
Fixed in
  • 1.7.4
GitHubfriendsofflarum/oauthpkg:github/friendsofflarum/oauthOther threatsAffected
  • <1.7.4
  • >=2.0.0-beta.1 <2.0.0-beta.4
Fixed in
  • 1.7.4
  • 2.0.0-beta.4

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

Community reviews

Loading reviews…