# CVE-2025-61783: Python Social Auth - Django has unsafe account association > Attackers can take over accounts by exploiting unsafe email association during authentication, even when the feature is disabled. - **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 9 Oct 2025 - **Updated:** 15 Oct 2025 - **Also known as:** DEBIAN-CVE-2025-61783, GHSA-wv4w-6qv2-qqfg, PYSEC-2026-1932, UBUNTU-CVE-2025-61783, openSUSE-SU-2026:10499-1 ## What is CVE-2025-61783? CVE-2025-61783 is a medium-severity authentication bypass vulnerability in python-social-auth social-app-django, published on 9 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-303 (Incorrect Implementation of Authentication Algorithm) ## Which versions are affected by CVE-2025-61783? 3 open source packages ship an affected version, including social-auth-app-django. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `social-auth-app-django` | PyPI | All versions | 5.6.0 | | `social-auth-app-django` | PyPI | All versions | 5.6.0 | | `social-auth-app-django` | PyPI | All versions | 5.6.0 | | `python-social-auth-app-django` | openSUSE:Tumbleweed | All versions | 5.7.0-1.1 | ## How do I fix CVE-2025-61783? Upgrade social-auth-app-django to 5.6.0 or later. ## Is CVE-2025-61783 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61783 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-61783 and fix it if it is affected. What it is: CVE-2025-61783 is a medium-severity authentication bypass vulnerability in python-social-auth social-app-django, published on 9 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61783 exists. Affected packages and fixed versions: - social-auth-app-django (PyPI): affected all versions; fixed in 5.6.0 - social-auth-app-django (PyPI): affected all versions; fixed in 5.6.0 - social-auth-app-django (PyPI): affected all versions; fixed in 5.6.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-61783/ (Markdown: https://insights.sbomify.com/CVE-2025-61783/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-61783 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-61783 - OSV: https://osv.dev/vulnerability/CVE-2025-61783 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-61783/ Summaries are generated and may contain mistakes; the official description above is the record.