Impact
Weblate’s API tokens, which are prefixed with “wlu_”, are not automatically revoked when a user changes their password. The existing browser sessions are invalidated correctly, but the tokens stored in the authtoken_token table continue to be valid. This flaw allows an attacker who has an active token before the password change to keep using that token for API calls after the account password has been updated. The vulnerability is a session‑fixation flaw and is classified as CWE‑613.
Affected Systems
Users running Weblate versions earlier than 5.17.1 are affected. All releases that contain the authtoken_token table with unrevoked API tokens are vulnerable, and the issue was patched in the 5.17.1 release. The product is the Weblate web‑based localization platform provided by WeblateOrg.
Risk and Exploitability
The CVSS score for this vulnerability is 4.2, indicating a medium impact. EPSS information is not available, and the vulnerability is not currently listed in the CISA KEV catalog. Because the flaw enables continued use of an API token after a password change, the likely attack vector is remote API exploitation; an attacker who has obtained or guessed a token before the password change can keep accessing the Weblate instance. The risk is moderate, but production deployments with exposed APIs or users who share long‑term tokens should address the issue promptly.
OpenCVE Enrichment
Github GHSA