FriendsOfFlarum OAuth: Unauthenticated account takeover via unverified email trust in Discord OAuth provider
Impact
An unauthenticated account takeover vulnerability exists in fof/oauth when the Discord OAuth provider is enabled.
Discord allows an account to use an unverified email address when its phone number has been verified. During OAuth authentication, Discord may return that email address with "verified": false.
Affected versions of fof/oauth did not validate this flag and passed the email address to Flarum core as trusted via provideTrustedEmail(). Flarum core could then match the trusted email address to an existing user, link the attacker-controlled Discord identity to that user, and authenticate the attacker as the victim.
An attacker who knows a user's email address can therefore take over the corresponding Flarum account without knowing its password or requiring any interaction from the victim. This includes administrator accounts.
Preconditions for exploitation
- Discord sign-in is enabled on the forum.
- The victim has a Flarum account with a known email address.
- The victim's email address is not already associated with a Discord account.
- The attacker creates or configures a Discord account using the victim's email address without verifying it and verifies a phone number instead.
- The attacker authenticates to the forum using that Discord account.
The issue is specific to Discord's ability to return an unverified email address through OAuth. Other bundled providers were not confirmed to be practically exploitable through the same method because they only return verified or confirmed email addresses in the relevant authentication flow.
Patched Versions
Workarounds
Administrators who cannot update immediately should disable the Discord OAuth provider in the extension settings.
Credits
Reported by @faran1512
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Composer package | fof/oauth | < 1.7.4, >= 2.0.0-beta.1, < 2.0.0-beta.4 | 1.7.4, 2.0.0-beta.4 |
References
- https://github.com/FriendsOfFlarum/oauth/security/advisories/GHSA-g7vj-c29h-3h5m
- https://nvd.nist.gov/vuln/detail/CVE-2026-92161
- https://github.com/FriendsOfFlarum/oauth/commit/baca3466b3b7be51c70a7e0ba966901aefeb344a
- https://github.com/FriendsOfFlarum/oauth/commit/bb4bf376832e6bb68c579715d2a4b5a92c4a2567
- https://github.com/FriendsOfFlarum/oauth
- https://github.com/FriendsOfFlarum/oauth/releases/tag/1.7.4
- https://github.com/FriendsOfFlarum/oauth/releases/tag/2.0.0-beta.4
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H- Weakness (CWE)
CWE-345- Platform
- Composer
- Package
fof/oauth- Disclosed
- 25.09.2026
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-g7vj-c29h-3h5m - CC BY 4.0
Vulnerability history: fof/oauth
All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.
This is the only known vulnerability of this package.
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.