wger: IDOR in RepetitionsConfig and MaxRepetitionsConfig API leak other users' workout data

Exploitation

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

CVSS

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

EPSS

• CVE-2026-27835: 0.29% estimated exploitation activity in the next 30 days; percentile 22.23 (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 RepetitionsConfigViewSet and MaxRepetitionsConfigViewSet return all users' repetition config data because their getqueryset() calls .all() instead of filtering by the authenticated user. Any registered user can enumerate every other user's workout structure. Details wger/manager/api/views.py:499 and :518: Every sibling viewset in the same file correctly filters by user. For example, WeightConfigViewSet at line 459: The same user filter is present on SetsConfig, RestConfig, RiRConfig, and their Max variants — only RepetitionsConfig and MaxRepetitionsConfig are missing it. PoC Registration is open by default. Sequential IDs allow full enumeration. Impact Any authenticated user can read other users' repetition and max-repetitions configs, exposing workout structure (slot entry IDs, iteration values, operations, step counts, repeat flags, requirements JSON). This is a broken object-level authorization (BOLA/IDOR) vulnerability — the same class of issue as OWASP API1. Fix: Add the…

Published by the source

26 Feb 2026, 22:13 UTC

Last modified by the source

13 Jul 2026, 16:42 UTC

Source last checked

26 Oct 2026, 13:36 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-xf68-8hjw-7mpm

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-xf68-8hjw-7mpm

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

# Patch Next advisory brief: CVE-2026-27835

Advisory: wger: IDOR in RepetitionsConfig and MaxRepetitionsConfig API leak other users' workout data
IDs: CVE-2026-27835, GHSA-xf68-8hjw-7mpm
Record: https://patchnext.com/advisories/cve-2026-27835 (revision 2, source checked 26 Oct 2026, 13:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
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-xf68-8hjw-7mpm (OSV record GHSA-xf68-8hjw-7mpm lists affected ranges: PyPI wger >=0 <=2.1)
- Verified: https://github.com/advisories/GHSA-xf68-8hjw-7mpm (GitHub-reviewed advisory GHSA-xf68-8hjw-7mpm lists affected ranges: PyPI wger >=0 <=2.1)

Commands are suggestions: review each one before running it.