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 SECURITYTOKENMAXAGE to "0" (seconds) which should make the token unusable.
// references
None
// cvss v3.1 vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None
Checked 2026-10-23 at 18:49 UTC. The most recent advisory here was published 2026-07-07. Updated continuously from NVD, GHSA, OSV and CNA feeds.