fof/oauth is vulnerable to Improper Authentication
74
CVE Score
High
Improper Authentication
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.
Upgrade the fof/oauth library to the patch version.
You are affected if you are using a version that falls within the vulnerable range.
1.4.0 - 1.7.4
Fixed in 1.8.0fof/oauth is vulnerable to Improper Authentication in versions 1.4.0 - 1.7.4.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.