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

Advisory record · `GHSA-x7qq-23vw-7pfg`

- **Identifiers:** `GHSA-x7qq-23vw-7pfg` · `CVE-2026-57177` · `PYSEC-2026-4169`
- **State:** Confirmed
- **Severity:** CVSS 4.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-352](https://cwe.mitre.org/data/definitions/352.html)
- **Tags:** [Cross-site request forgery (CSRF)](https://agentprime.io/advisories/tag/csrf.md)
- **Published:** 24 Sept 2026
- **Updated:** 1 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 24 Sept 2026, 19:56 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `social-auth-core` (PyPI): affected `<5.0.0`; fixed in `5.0.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The social-auth-core package, versions before 5.0.0, is vulnerable to login CSRF in its LoginRadius backend, which did not validate the OAuth state during authentication. An attacker can get a victim's browser session to complete login with an attacker-controlled LoginRadius token, authenticating the victim as the attacker's identity. Upgrade to version 5.0.0 or later; disabling the LoginRadius backend by removing it from SOCIAL_AUTH_AUTHENTICATION_BACKENDS is the only workaround, and it is only available if the backend is not needed.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 4.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0011, the 1st percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:09 UTC: First seen by agentprime
- 31 Oct 2026, 14:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-x7qq-23vw-7pfg)

## Sources

- [GitHub Advisory Database: GHSA-x7qq-23vw-7pfg](https://github.com/advisories/GHSA-x7qq-23vw-7pfg)
- [OSV: GHSA-x7qq-23vw-7pfg](https://osv.dev/vulnerability/GHSA-x7qq-23vw-7pfg)
- <https://github.com/python-social-auth/social-core/security/advisories/GHSA-x7qq-23vw-7pfg>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-57177>
- <https://github.com/python-social-auth/social-core/pull/1808>
- <https://github.com/python-social-auth/social-core/commit/4d332820e6b0583fde522956105a0e2beced5335>
- <https://github.com/python-social-auth/social-core>
- <https://github.com/python-social-auth/social-core/releases/tag/5.0.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-x7qq-23vw-7pfg>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-x7qq-23vw-7pfg/>. Everything for agents: <https://agentprime.io/llms.txt>.