Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.5amended

wger: cross-tenant account deletion / deactivation / activation by gym.manage_gym + gym=None

GHSA-mw8f-w6p8-xrf4

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI wger

    Affected
    <= 2.5
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.5 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary GHSA-mhc8-p3jx-84mm (CVE-2026-43948) reported that wger's resetuserpassword and gympermissionsuseredit views in wger/gym/views/user.py performed a gym-scope authorization check using Django ORM object comparison (if request.user.userprofile.gym != user.userprofile.gym) which silently passes when both sides are None (None != None evaluates to False). The maintainer's suggested patch ("Apply the same samegym() helper pattern to all five views sharing this check") replaces every userprofile.gym != site with the new issamegym() helper that explicitly excludes None (gyma is not None and gyma == gymb). The fix landed in wger/gym/views/{adminnotes,document,contract,gym}.py (5 views, all using issamegym). However, three additional views in wger/core/views/user.py were not migrated and retain the original userprofile.gymid != ... raw integer comparison. Because raw integer != comparison still evaluates None != None as False, the gym-scope guard is bypassed identically to the patched…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-mw8f-w6p8-xrf4

  2. Revision 1 · created ·

    Published from osv record GHSA-mw8f-w6p8-xrf4

Agent brief

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

# Patch Next advisory brief: GHSA-mw8f-w6p8-xrf4

Advisory: wger: cross-tenant account deletion / deactivation / activation by gym.manage_gym + gym=None
IDs: GHSA-mw8f-w6p8-xrf4
Record: https://patchnext.com/advisories/ghsa-mw8f-w6p8-xrf4 (revision 2, source checked 26 Oct 2026, 13:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.5)
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.5

## 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://osv.dev/vulnerability/GHSA-mw8f-w6p8-xrf4 (OSV record GHSA-mw8f-w6p8-xrf4 lists affected ranges: PyPI wger >=0 <=2.5)
- Verified: https://github.com/advisories/GHSA-mw8f-w6p8-xrf4 (GitHub-reviewed advisory GHSA-mw8f-w6p8-xrf4 lists affected ranges: PyPI wger >=0 <=2.5)

Commands are suggestions: review each one before running it.

Loading voting…