Read the docs
TI-2026-62240 Aliases CVE-2026-92161GHSA-g7vj-c29h-3h5m

FriendsOfFlarum OAuth: Unauthenticated account takeover via unverified email trust in Discord OAuth provider

Priority MEDIUM 49CWE-345Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-345.

Summary

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00272 19th percentileScored 2026-11-07
Fix Fixed oauth (FriendsOfFlarum): 1.7.4, 2.0.0-beta.4fof/oauth (Packagist): 1.7.4, 2.0.0-beta.4

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
FriendsOfFlarumoauthbefore 1.7.4; 2.0.0-beta.1 to before 2.0.0-beta.41.7.4, 2.0.0-beta.4Patch availableCNA
—fof/oauth (Packagist)before 1.7.41.7.4Patch availableGHSA-g7vj-c29h-3h5m
—fof/oauth (Packagist)2.0.0-beta.1 to before 2.0.0-beta.42.0.0-beta.4Patch availableGHSA-g7vj-c29h-3h5m
  • oauth VendorFriendsOfFlarum Affected before 1.7.4; 2.0.0-beta.1 to before 2.0.0-beta.4 Fixed in 1.7.4, 2.0.0-beta.4 Patch available CNA
  • fof/oauth (Packagist) Vendor— Affected before 1.7.4 Fixed in 1.7.4 Patch available GHSA-g7vj-c29h-3h5m
  • fof/oauth (Packagist) Vendor— Affected 2.0.0-beta.1 to before 2.0.0-beta.4 Fixed in 2.0.0-beta.4 Patch available GHSA-g7vj-c29h-3h5m

Remediation

  • Fix · CNA oauth (FriendsOfFlarum) Fixed in 1.7.4, 2.0.0-beta.4
  • Fix · GHSA-g7vj-c29h-3h5m fof/oauth (Packagist) Fixed in 1.7.4 Advisory →
  • Fix · GHSA-g7vj-c29h-3h5m fof/oauth (Packagist) Fixed in 2.0.0-beta.4 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-92161
  2. 2026-10-03 Alias added: GHSA-g7vj-c29h-3h5m

References

  • TI-2022-13045 Possible cross-site scripting attack via unsanitized SVG files in FoF Upload CVSS 3.1HIGH 8.7
  • TI-2022-16348 User preference to prevent private discussions not respected in fof/byobu CVSS 3.1MEDIUM 4.3

Sources