python-social-auth social-app-django up to 5.5.x Authentication Service associate_by_email incorrect implementation of authentication algorithm
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in python-social-auth social-app-django up to 5.5.x. It has been rated as problematic. The affected element is the function associate_by_email of the component Authentication Service Handler. This manipulation causes incorrect implementation of authentication algorithm.
This vulnerability is tracked as CVE-2025-61783. The attack is possible to be carried out remotely. No exploit exists.
Upgrading the affected component is advised.
Details
A vulnerability classified as problematic was found in python-social-auth social-app-django up to 5.5.x. Affected by this vulnerability is the function associate_by_email of the component Authentication Service Handler. The manipulation with an unknown input leads to a incorrect implementation of authentication algorithm vulnerability. The CWE definition for the vulnerability is CWE-303. The requirements for the product dictate the use of an established authentication algorithm, but the implementation of the algorithm is incorrect. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at github.com. This vulnerability is known as CVE-2025-61783 since 09/30/2025. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.
Upgrading to version 5.6.0 eliminates this vulnerability. Applying the patch 10c80e2ebabeccd4e9c84ad0e16e1db74148ed4c is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Incorrect implementation of authentication algorithmCWE: CWE-303
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: social-app-django 5.6.0
Patch: 10c80e2ebabeccd4e9c84ad0e16e1db74148ed4c
Timeline
09/30/2025 CVE reserved10/10/2025 Advisory disclosed
10/10/2025 VulDB entry created
10/10/2025 VulDB entry last update
Sources
Product: github.comAdvisory: 220
Status: Confirmed
CVE: CVE-2025-61783 (🔒)
GCVE (CVE): GCVE-0-2025-61783
GCVE (VulDB): GCVE-100-327817
Entry
Created: 10/10/2025 08:29Changes: 10/10/2025 08:29 (71)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.