wger: API credentials remain valid after logout/password change

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.8 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS

• CVE-2026-46437: 0.24% estimated exploitation activity in the next 30 days; percentile 15.47 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A vulnerability exists in the authentication/session lifecycle of wger where bearer-style API credentials remain valid after a user logs out and after a user changes their password. An attacker who steals a victim’s DRF authtoken (Authorization: Token ...) or JWT refresh token can continue to access protected /api/v2/ endpoints until the token is manually rotated/deleted (DRF token) or naturally expires (JWT refresh). lifecycle events do not revoke these credentials: - Logout (/user/logout) only clears the Django session cookie via djangologout() and does not revoke API tokens. - Password change updates the password hash, but does not revoke: - existing DRF tokens stored in authtokentoken - existing JWT refresh tokens (no server-side revocation list or token versioning); refresh can continue minting new access tokens until refresh expiry. Vulnerable Files - wger/wger/core/views/user.py (logout implementation) - wger/settings/settingsglobal.py (DRF auth configuration,…

Published by the source

7 Oct 2026, 13:59 UTC

Last modified by the source

15 Oct 2026, 14:55 UTC

Source last checked

26 Oct 2026, 13:55 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-v3x9-6gg8-c2c9

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-v3x9-6gg8-c2c9

3. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-v3x9-6gg8-c2c9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-46437

Advisory: wger: API credentials remain valid after logout/password change
IDs: CVE-2026-46437, GHSA-v3x9-6gg8-c2c9
Record: https://patchnext.com/advisories/cve-2026-46437 (revision 3, source checked 26 Oct 2026, 13:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI wger: affected <= 2.1

## Suggested inspection (read-only)
- `python -m pip show wger`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on wger.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-v3x9-6gg8-c2c9 (GitHub-reviewed advisory GHSA-v3x9-6gg8-c2c9 lists affected ranges: PyPI wger >=0 <=2.1)
- Verified: https://osv.dev/vulnerability/GHSA-v3x9-6gg8-c2c9 (OSV record GHSA-v3x9-6gg8-c2c9 lists affected ranges: PyPI wger >=0 <=2.1)

Commands are suggestions: review each one before running it.