GHSA-g7vj-c29h-3h5m

Source

https://github.com/advisories/GHSA-g7vj-c29h-3h5m

Import Source

https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/09/GHSA-g7vj-c29h-3h5m/GHSA-g7vj-c29h-3h5m.json

JSON Data

https://api.osv.dev/v1/vulns/GHSA-g7vj-c29h-3h5m

Aliases

CVE-2026-92161

Published

2026-09-25T15:55:07Z

Modified

2026-09-25T20:45:04Z

Severity

9.8 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CVSS Calculator

Summary

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

Details

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

Database specific

{
    "cwe_ids":  [
        "CWE-345"
    ],
    "github_reviewed":  true,
    "github_reviewed_at":  "2026-09-25T15:55:07Z",
    "nvd_published_at":  "2026-09-25T16:17:29Z",
    "severity":  "CRITICAL"
}

References

Affected packages

Packagist / fof/oauth

Package

Name: fof/oauth
Purl: pkg:composer/fof/oauth

Affected ranges

Type: ECOSYSTEM
Events: Introduced

0 Unknown introduced version / All previous versions are affected

Fixed

1.7.4

Affected versions

0.*

0.1.0

0.2.0

0.2.1

0.3.0

1.*

1.0.0

1.0.1

1.0.2

1.1.0

1.1.1

1.2.0

1.2.1

1.2.2

1.2.3

1.2.4

1.2.5

1.3.0

1.3.1

1.3.2

1.4.0

1.4.1

1.4.2

1.4.3

1.4.4

1.5.0

1.5.1

1.5.2

1.5.3

1.5.4

1.6.1

1.6.2

1.6.3

1.6.4

1.6.5

1.6.6

1.6.7

1.6.8

1.6.9

1.6.10

1.6.11

1.6.12

1.6.13

1.6.14

1.6.16

1.7.0

1.7.1

1.7.2

1.7.3

Database specific

source

"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/09/GHSA-g7vj-c29h-3h5m/GHSA-g7vj-c29h-3h5m.json"

Packagist / fof/oauth

Package

Name: fof/oauth
Purl: pkg:composer/fof/oauth

Affected ranges

Type: ECOSYSTEM
Events: Introduced

2.0.0-beta.1

Fixed

2.0.0-beta.4

Affected versions

2.*

2.0.0-beta.1

2.0.0-beta.2

2.0.0-beta.3

Database specific

source

"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/09/GHSA-g7vj-c29h-3h5m/GHSA-g7vj-c29h-3h5m.json"