CVE Explore

CSRF in Fastapi-Users

CVE-2025-68481

CVSS v3
5.9 Medium
Public exploits
None known
EPSS
0.003 · 17.7th percentile
Published
2025-12-19

What to do

Fixed in
15.0.2
Affected
2 affected products

FastAPI Users allows users to quickly add a registration and authentication system to their FastAPI project. Prior to version 15.0.2, the OAuth login state tokens are completely stateless and carry no per-request entropy or any data that could link them to the session that initiated the OAuth flow. `generate_state_token()` is always called with an empty `state_data` dict, so the resulting JWT only contains the fixed audience claim plus an expiration timestamp. On callback, the library merely checks that the JWT verifies under `state_secret` and is unexpired; there is no attempt to match the state value to the browser that initiated the OAuth request, no correlation cookie, and no server-side cache. Any attacker can hit `/authorize`, capture the server-generated state, finish the upstream OAuth flow with their own provider account, and then trick a victim into loading `.../callback?code=<attacker_code>&state=<attacker_state>`. Because the state JWT is valid for any client for \~1 hour, the victim’s browser will complete the flow. This leads to login CSRF. Depending on the app’s logic, the login CSRF can lead to an account takeover of the victim account or to the victim user getting logged in to the attacker's account. Version 15.0.2 contains a patch for the issue.

Published · last modified .

CVSS v3 metric

CVSS v3 base score 5.9 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N.

Attack Vector
Network AV:N
Attack Complexity
High AC:H
Privileges Required
None PR:N
User Interaction
Required UI:R
Scope
Unchanged S:U
Confidentiality
High C:H
Integrity
Low I:L
Availability
None A:N

EPSS exploit prediction

EPSS 0.003, 17.7th percentile (last changed ); unchanged over 30 days. About EPSS.

Affected products

Weakness classification (CWE)

References