Quick answers
- Is CVE-2026-43948 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-43948 being exploited in the wild.
- How severe is CVE-2026-43948?
- Critical severity, with a CVSS score of 9.9, published 12 May 2026.
- Which products and versions are affected?
- wger (PyPI) <= 2.5, ECOSYSTEM:introduced=0,fixed=2.6.
- Is there a fix for CVE-2026-43948?
- Yes. wger (PyPI): upgrade to 2.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-43948 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-43948?
- Check whether you run wger (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- wger (PyPI): upgrade to 2.6 or later
pip install "wger>=2.6"
Technical details
The reset_user_password and gym_permissions_user_edit views in wger's gym/views/user.py perform a gym-scope authorization check using Python's inequality operator (!=). When both the attacker and the target user have no gym assigned (gym=None), the comparison 'None != None' evaluates to False, causing the authorization guard to be bypassed. An attacker with 'gym.manage_gym' permissions can trigger a password reset for any other unaffiliated user; the application then generates a new password and returns it in plaintext within the HTML response body. This results in a full account takeover and permanent lockout of the victim. The issue is fixed in version 2.6 by using raw foreign key comparisons and explicit null checks.
Affected products
- wger-project wger < 2.6
Identifiers
- CVE-2026-43948
- GHSA-mhc8-p3jx-84mm
- PYSEC-2026-574
Timeline
- 2026-04-28: advisory: GitHub Security Advisory published
- 2026-05-12: disclosed: CVE published to NVD
- 2026-05-12: patched: Vulnerability fixed in version 2.6