Summary
Python Social Auth - Django has unsafe account association
Workarounds
Review the authentication service policy on e-mail addresses; many will not allow exploiting this vulnerability.
Impact
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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Frequently Asked Questions
- What is CVE-2025-61783? CVE-2025-61783 is a medium-severity security vulnerability in social-auth-app-django (pip), affecting versions < 5.6.0. It is fixed in 5.6.0.
- Which versions of social-auth-app-django are affected by CVE-2025-61783? social-auth-app-django (pip) versions < 5.6.0 is affected.
- Is there a fix for CVE-2025-61783? Yes. CVE-2025-61783 is fixed in 5.6.0. Upgrade to this version or later.
- Is CVE-2025-61783 exploitable, and should I be worried? Whether CVE-2025-61783 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-61783 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-61783? Upgrade
social-auth-app-djangoto 5.6.0 or later.