CVE-2026-57177

social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend

Published Sep 24, 2026 CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
Description
Python Social Auth is a social authentication/registration mechanism. Prior to version 5.0.0, the LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. The issue has been fixe in version 5.0.0 by enabling callback state validation for the LoginRadius backend.

Analysis

AI-generated

Technical impact

Python Social Auth’s LoginRadius backend previously failed to validate the OAuth state parameter during authentication. This omission enabled a login CSRF attack, letting an attacker coercively complete a user’s login flow with an attacker-controlled token, effectively authenticating the victim as the attacker’s LoginRadius account. The resulting impact is unauthorized access to the victim’s session and any resources tied to that identity.

Affected Systems

Applications that integrate the python-social-auth:social-core package via its LoginRadius backend and are running a version older than 5.0.0 are susceptible. Versions 5.0.0 and newer include state validation, rendering the issue resolved.

Risk and Exploitability

The calculated CVSS score of 4.3 indicates moderate severity. The EPSS score is < 1%, and the vulnerability is not listed in the CISA KEV catalog. The attack vector is inferred to be a social login flow where the attacker supplies a forged authentication request, exploiting the missing state check.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade python-social-auth to version 5.0.0 or later
  • Verify that state validation is enabled for the LoginRadius backend in the deployment configuration
  • If upgrading is not immediately possible, disable the LoginRadius backend or restrict its usage to mitigate CSRF risk

Generated by OpenCVE AI on September 26, 2026 at 00:28 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-x7qq-23vw-7pfg social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Python-social-auth
Python-social-auth social-core
Vendors & Products Python-social-auth
Python-social-auth social-core
Type Values Removed Values Added
Description Python Social Auth is a social authentication/registration mechanism. Prior to version 5.0.0, the LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. The issue has been fixe in version 5.0.0 by enabling callback state validation for the LoginRadius backend.
Title social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
Weaknesses CWE-352
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N'}

Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)

  • CWE-358

    Improperly Implemented Security Check for Standard

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 5, 2026, 3:33 PM
Reserved
Jun 24, 2026, 1:47 AM
Status
Awaiting Analysis
Published
Sep 24, 2026, 6:17 PM
Modified
Oct 5, 2026, 4:17 PM
Severity
Moderate
Public date
Sep 24, 2026, 5:24 PM