dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-43948

CRITICAL · 9.9 CVSS v3.1 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
wger is a free, open-source workout and fitness manager. Prior to 2.6, the reset_user_password and gym_permissions_user_edit views in wger perform a gym-scope authorization check using Python object comparison (!=) that evaluates None != None as False, silently bypassing the guard when both the attacker and victim have no gym assignment (gym=None). A user with gym.manage_gym permission and gym=None can reset the password of any other gym=None user; the new plaintext password is returned verbatim in the HTML response body, enabling one-shot full account takeover. The victim's original password is invalidated, locking them out permanently. This vulnerability is fixed in 2.6.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The wger fitness manager application has a flawed authorization check in the reset_user_password and gym_permissions_user_edit views that uses Python's != operator. When both attacker and victim have gym=None, the check None != None evaluates to False, bypassing the authorization guard. An attacker with gym.manage_gym permission but gym=None can reset any other user's password with gym=None, receiving the plaintext new password in the response for immediate account takeover.

MitigationUpgrade to wger version 2.6 or later which contains the patched authorization logic.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm wger fitness manager is installed
    Identify if the wger application is running in your environment. Check for wger-related processes, services, or web applications.
    Affected if wger fitness manager is present and accessible
  2. Determine installed wger version
    Locate and read the version file or check the application's about/version page. Compare the version number to the 2.6 threshold.
    Affected if The installed version is below 2.6 (e.g., 2.5.x, 2.4.x, etc.)
  3. Identify users with manage_gym permission and gym=None
    Query the user database or user management interface to find accounts that have the gym.manage_gym permission assigned while their associated gym field is set to None (null).
    Affected if There exists at least one user with gym=None and gym.manage_gym permission, other than the currently logged-in user
  4. Test reset_user_password view accessibility
    Attempt to access or send a request to the reset_user_password view endpoint, preferably with a different gym=None user account that has manage_gym permission.
    Affected if The view is accessible and responds without proper authorization validation for gym-scope checks
  5. Verify plaintext password in response
    After triggering a password reset through the vulnerable view, inspect the HTTP response or HTML output to check if the new password is returned in plaintext.
    Affected if The plaintext new password appears in the response body, indicating the information disclosure component is present

If wger fitness manager version is below 2.6 and you have users with gym=None combined with gym.manage_gym permission, the authorization bypass vulnerability is likely present and exploitable.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to wger version 2.6 or later which contains the patched authorization logic.

Recommended fix High confidence

2.6

  1. Check current wger version by inspecting the installed package or checking the application UI
  2. Backup the wger database before upgrading to ensure data safety
  3. Upgrade wger to version 2.6 using the installation method in use (e.g., pip install wger==2.6 for pip installations, or pull the updated Docker image, or git checkout v2.6 for source installations)
  4. Run any required database migrations after upgrade (e.g., python manage.py migrate)
  5. Restart the wger application service to load the updated code
  6. Verify the application is running version 2.6 and that the password reset functionality now correctly enforces gym-scope authorization
Caveat Review the wger 2.6 release notes for any breaking changes or deprecations before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-43948 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-43948 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data