Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-wv4w-6qv2-qqfg | Python Social Auth - Django has unsafe account association |
Wed, 15 Oct 2025 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 10 Oct 2025 12:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
Fri, 10 Oct 2025 11:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Python-social-auth
Python-social-auth social-app-django |
|
| Vendors & Products |
Python-social-auth
Python-social-auth social-app-django |
Thu, 09 Oct 2025 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Python Social Auth - Django has unsafe account association | |
| Weaknesses | CWE-303 | |
| References |
|
|
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2025-10-15T19:49:22.392Z
Reserved: 2025-09-30T19:43:49.902Z
Link: CVE-2025-61783
Updated: 2025-10-15T19:48:58.459Z
Status : Deferred
Published: 2025-10-09T21:15:40.127
Modified: 2026-04-15T00:35:42.020
Link: CVE-2025-61783
OpenCVE Enrichment
Updated: 2025-10-10T11:17:32Z
Github GHSA