CVE-2026-92161

Critical

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.

SeverityCritical
CVSS9.8
Exploit probability—
ProductFof/oauth
PublishedSep 25, 2026
First seenSep 25, 2026
Weakness typeCWE-345CWE-345

How to fix

Update
  • fof/oauth1.7.4, 2.0.0-beta.4 or later

Affected products

ProductAffected versionsFixed in
fof/oauthPackagistv < 1.7.4, 2.0.0-beta.1 ≤ v < 2.0.0-beta.41.7.4, 2.0.0-beta.4

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.