CVE-2026-62322: CWE-352: Cross-Site Request Forgery (CSRF) in python-social-auth social-core
Description
A Cross-Site Request Forgery (CSRF) vulnerability exists in python-social-auth's social-core LINE backend prior to version 5.0.2. The vulnerability arises because the LINE backend exchanges an authorization code without validating the returned OAuth state parameter. This flaw allows an attacker to cause a victim to be logged into the attacker's LINE account or link the attacker's LINE identity to the victim's existing account when account linking is enabled. This creates a persistent unauthorized login path. The issue is fixed in version 5.0.2.
CVSS v3.1
Score 6.5medium
Affected software
python-social-auth
social-core
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The python-social-auth social-core LINE backend prior to version 5.0.2 does not validate the OAuth state parameter during the authorization code exchange. This missing validation enables a Cross-Site Request Forgery (CWE-352) attack where an attacker can initiate authorization for their own LINE account and trick a victim into visiting the callback URL. Consequently, the victim's session is logged into the attacker's LINE account. If account linking is enabled, the attacker can link their LINE identity to the victim's account, creating a persistent unauthorized access vector. This vulnerability affects only applications with the LINE backend enabled and is resolved in version 5.0.2.
Potential Impact
An attacker can cause a victim to be logged into the attacker's LINE account without the victim's consent, potentially leading to unauthorized access or session confusion. When account linking is enabled, the attacker can link their LINE identity to the victim's account, creating a persistent unauthorized login path. There is no direct confidentiality or availability impact reported. The CVSS 3.1 base score is 6.5 (medium severity), reflecting the impact on integrity with no confidentiality or availability impact.
Mitigation Recommendations
Upgrade python-social-auth social-core to version 5.0.2 or later, where the issue is fixed by validating the OAuth state parameter during the authorization code exchange. Applications using the LINE backend should ensure they are not running affected versions prior to 5.0.2. No other mitigations are specified.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-13T19:27:58.314Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ad123c12cdf04f65652b7b3
Added to database: 10/15/2026, 19:04:33 UTC
Last enriched: 10/15/2026, 19:18:48 UTC
Last updated: 10/15/2026, 19:19:21 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.