Skip to content
Fencer Vulns
medium 6.3

CVE-2025-61783 json

Python Social Auth - Django has unsafe account association

published 2025-10-09 13 mo ago modified 2026-10-08 31 d ago also GHSA-wv4w-6qv2-qqfg , PYSEC-2026-1932 , EUVD-2025-33405

cvss
6.3
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 45%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi social-auth-app-django 5.6.0
  • python-social-auth-app-django openSUSE Tumbleweed 5.7.0-1.1

opensuse advisories openSUSE-SU-2026:10499-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-61783 updated cvss 4.8

social-app-django: Python Social Auth - Django has unsafe account association

  • Red Hat Ansible Automation Platform 2 python-social-auth-app-django, python3x-social-auth-app-django, python3.11-social-auth-app-django Red Hat Satellite 6 python-social-auth-app-django
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
12 mo ago

Exploit prediction

0.54% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/python-social-auth/social-app-django/issues/220 referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/python-social-auth/social-app-django/issues/231 referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/python-social-auth/social-app-django/issues/634 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 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
CNA 4.0 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
pypi social-auth-app-django
<5.6.0
5.6.0

Affected products

  • python-social-auth social-app-django

Classification

Weakness
  • CWE-303 Incorrect Implementation of Authentication Algorithm
  • CWE-290 Authentication Bypass by Spoofing

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.