Most recent entries from all

EUVD-2026-22074

fkie_cve-2021-21241

The Python "Flask-Security-Too" package is used for adding security features to your Flask application. It is an is a independently maintained version of Flask-Security based on the 3.0.0 version of Flask-Security. In Flask-Security-Too from version 3.3.0 and before version 3.4.5, the /login and /change endpoints can return the authenticated user's authentication token in response to a GET request. Since GET requests aren't protected with a CSRF token, this could lead to a malicious 3rd party site acquiring the authentication token. Version 3.4.5 and version 4.0.0 are patched. As a workaround, if you aren't using authentication tokens - you can set the SECURITY_TOKEN_MAX_AGE to "0" (seconds) which should make the token unusable.

GHSA-hh7m-rx4f-4vpv — CSRF can expose users authentication token

Affected: PyPI: Flask-Security-Too

### Issue The /login and /change endpoints can return the authenticated user's authentication token in response to a GET request. Since GET requests aren't protected with a CSRF token, this could lead to a malicious 3rd party site acquiring the authentication token.

### Patches Version 3.4.5 and soon to be released 4.0.0 are patched.

### Workarounds If you aren't using authentication tokens - you can set the SECURITY_TOKEN_MAX_AGE to "0" (seconds) which should make the token unusable.

### References None

gsd-2021-21241

openSUSE-SU-2024:13561-1 — python310-Flask-Security-Too-5.3.2-3.1 on GA media

python310-Flask-Security-Too-5.3.2-3.1 on GA media

PYSEC-2021-91

Affected: PyPI: flask-security-too