wger has Broken Access Control in Global Gym Configuration Update Endpoint

Exploitation

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

CVSS

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

EPSS

• CVE-2026-40474: 0.33% estimated exploitation activity in the next 30 days; percentile 26.58 (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 wger exposes a global configuration edit endpoint at /config/gym-config/edit implemented by GymConfigUpdateView. The view declares permissionrequired = 'config.changegymconfig' but does not enforce it because it inherits WgerFormMixin (ownership-only checks) instead of the project’s permission-enforcing mixin (WgerPermissionMixin) . The edited object is a singleton (GymConfig(pk=1)) and the model does not implement getownerobject(), so WgerFormMixin skips ownership enforcement. As a result, a low-privileged authenticated user can modify installation-wide configuration and trigger server-side side effects in GymConfig.save(). This is a vertical privilege escalation from a regular user to privileged global configuration control. The application explicitly declares permissionrequired = 'config.changegymconfig', demonstrating that the action is intended to be restricted; however, this requirement is never enforced at runtime. Affected endpoint The config URLs map as follows.…

Published by the source

16 Apr 2026, 01:35 UTC

Last modified by the source

13 Jul 2026, 16:42 UTC

Source last checked

26 Oct 2026, 13:40 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-xppv-4jrx-qf8m

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-xppv-4jrx-qf8m

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

# Patch Next advisory brief: CVE-2026-40474

Advisory: wger has Broken Access Control in Global Gym Configuration Update Endpoint
IDs: CVE-2026-40474, GHSA-xppv-4jrx-qf8m
Record: https://patchnext.com/advisories/cve-2026-40474 (revision 2, source checked 26 Oct 2026, 13:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.6)
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://osv.dev/vulnerability/GHSA-xppv-4jrx-qf8m (OSV record GHSA-xppv-4jrx-qf8m lists affected ranges: PyPI wger >=0 <=2.1)
- Verified: https://github.com/advisories/GHSA-xppv-4jrx-qf8m (GitHub-reviewed advisory GHSA-xppv-4jrx-qf8m lists affected ranges: PyPI wger >=0 <=2.1)

Commands are suggestions: review each one before running it.