CVE-2025-61783: python-social-auth social-app-django · Incorrect Implementation of Authentication Algorithm
Affects python-social-auth social-app-djangoSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 5.6.0 when convenient.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.6.0
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade python-social-auth social-app-django to 5.6.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| python-social-auth social-app-django | Affected
| Fixed in
|
AI-suggested
- Upgrade all instances of social-app-django to version 5.6.0 or later, where the vulnerability is patched.
- Conduct a thorough review of all third-party authentication providers integrated with your systems to ensure they enforce strict email validation and uniqueness policies.
- Implement additional verification steps in the authentication pipeline, such as multi-factor authentication (MFA), to reduce the risk of account compromise even if email association is exploited.
- Audit existing user accounts for suspicious activity or unauthorized access that might have resulted from this vulnerability.
- Consider customizing the authentication pipeline to explicitly disable or control email-based association if not required.
- Monitor security advisories and logs for any anomalous authentication attempts that could indicate exploitation attempts.
- Educate development and security teams about the risks of relying solely on email for user association in social authentication flows.
Description
Python Social Auth is a social authentication/registration mechanism. In versions prior to 5.6.0, upon authentication, the user could be associated by e-mail even if the `associate_by_email` pipeline was not included. This could lead to account compromise when a third-party authentication service does not validate provided e-mail addresses or doesn't require unique e-mail addresses. Version 5.6.0 contains a patch. As a workaround, review the authentication service policy on e-mail addresses; many will not allow exploiting this vulnerability.
References
- github.com/python-social-auth/social-app-django/security/advisories/GHSA-wv4w-6qv2-qqfg (opens in a new tab)
- github.com/python-social-auth/social-app-django/issues/220 (opens in a new tab)
- github.com/python-social-auth/social-app-django/issues/231 (opens in a new tab)
- github.com/python-social-auth/social-app-django/issues/634 (opens in a new tab)
- github.com/python-social-auth/social-app-django/pull/803 (opens in a new tab)
- github.com/python-social-auth/social-app-django/commit/10c80e2ebabeccd4e9c84ad0e16e1db74148ed4c (opens in a new tab)