Intel

AIKIDO-2026-276117

fof/oauth is vulnerable to Improper Authentication

Improper AuthenticationGHSA-88pg-6p5r-5cpr Published Yesterday

74

High Risk

This Affects:

PHPfof/oauth
1.4.0 - 1.7.4
Fixed in 1.8.0
Are you affected? Scan for Free

TL;DR

fof/oauth's email sync listener and several providers use an OAuth provider's reported email as a confirmed address without checking whether the provider itself verified it. With update_email_from_provider enabled (the default), CheckAndUpdateUserEmail::handle() calls changeEmail() directly on every login or account link, replacing the forum account's email and leaving is_email_confirmed untouched, so an unverified provider reported address becomes a confirmed forum email. The GitHub provider's suggestions() similarly passes the public, unverified GET /user email to provideTrustedEmail(), letting that address log in to or link an existing forum account. The fix adds a getProviderVerifiedEmail() check per provider and passes provider driven email changes through Flarum's confirmation email flow instead of changing the email directly.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range.

Background info

fof/oauth is vulnerable to Improper Authentication in versions 1.4.0 - 1.7.4.

How to fix this

Upgrade the fof/oauth library to the patch version.

Are You Affected?

Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.

Free. No credit card required.

Aikido Platform