GHSA-ffhx-3gqx-873h json
FacebookAppOAuth2 backend allows login CSRF via missing validate_state() call
published last mo. modified last mo.
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository python-social-auth/social-core. GitHub has not reviewed it into the GitHub Advisory Database and no CVE record has reached us yet, so everything here comes from the maintainers alone. Read the full advisory on GitHub.
- cvss
- 8.1
- version 3.1, the maintainers
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
Security advisory published by the maintainers of python-social-auth/social-core for social-auth-core: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.
Is GHSA-ffhx-3gqx-873h in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| the maintainers | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | social-auth-core | <=5.1.1 |
no fix listed |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
Sources
- Maintainer advisory GHSA-ffhx-3gqx-873h
Fencer Intel 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.
The maintainers of python-social-auth/social-core published their own advisory on GitHub. Its facts and headline are shown here; the description stays on GitHub.