← Back
CVE-2025-61783
Vulnerability in social-auth-app-django (CVE-2025-61783)
Summary
vulnerability in social-auth-app-django (CVE-2025-61783). Risk of unauthorized operations or information disclosure. Exploitable via ``associate_by_email``. Mitigation: upgrade to `5.6.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-61783** has been found in social-auth-app-django.
Attackers can target a specific entry point like ``associate_by_email`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade social-auth-app-django to **5.6.0** or later.
If unsure, ask your IT team or search "social-auth-app-django CVE-2025-61783" on the vendor's site.
CVE-2025-61783 (social-auth-app-django) — CWE-290 /
Attack surface: `associate_by_email`
Patched: `5.6.0` — apply immediately
Workaround: Review the authentication service policy on e-mail addresses; many will not allow exploiting this vulnerability.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-290) exists in social-auth-app-django. Attackers reach the vulnerable code path via ``associate_by_email`` without authentication.
📍 Affected scope
social-auth-app-django — . Attack surface: `associate_by_email`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5.6.0**.
🛡️ Workaround
Workaround: Review the authentication service policy on e-mail addresses; many will not allow exploiting this vulnerability.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'social-auth-app-django' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'social-auth-app-django' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `social-auth-app-django` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Review the authentication service policy on e-mail addresses; many will not allow exploiting this vulnerability.パッチが適用されるまでの応急処置として、Review the authentication service policy on e-mail addresses; many will not allow exploiting this vulnerability. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade social-auth-app-django to 5.6.0ステージング環境で 5.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
social-auth-app-django
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.6.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-61783
- advisory https://github.com/advisories/GHSA-wv4w-6qv2-qqfg
- package https://github.com/python-social-auth/social-app-django
- package https://pypi.org/project/social-auth-app-django
- web https://github.com/python-social-auth/social-app-django/security/advisories/GHSA-wv4w-6qv2-qqfg
- web https://github.com/python-social-auth/social-app-django/issues/220
- web https://github.com/python-social-auth/social-app-django/issues/231
- web https://github.com/python-social-auth/social-app-django/issues/634
- web https://github.com/python-social-auth/social-app-django/pull/803
- web https://github.com/python-social-auth/social-app-django/commit/10c80e2ebabeccd4e9c84ad0e16e1db74148ed4c