wger: Cross-User Data Corruption via Missing Ownership Check on WorkoutLog.slot_entry

Exploitation

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

CVSS

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

EPSS

• CVE-2026-46438: 0.23% estimated exploitation activity in the next 30 days; percentile 13.51 (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 An authenticated attacker can inject arbitrary workout log entries into any other user's `SlotEntry` by supplying the victim's `slot_entry` ID in a `POST /api/v2/workoutlog/` request. The `slot_entry` foreign key is not included in the ownership verification performed by `WorkoutLogViewSet.get_owner_objects()`, so the server accepts and persists the cross-user reference without error. Because `SlotEntry.get_config_data()` retrieves associated logs via `self.workoutlog_set.all()` with no user filter, the attacker's injected data is silently folded into the victim's progressive-overload calculations, corrupting their auto-generated weight and repetition targets.

Details wger uses a centralized ownership-verification pattern in `WgerOwnerObjectModelViewSet.create()` (file: `wger/utils/viewsets.py`). This method iterates over the list returned by each ViewSet's `get_owner_objects()` and verifies that every listed foreign-key value in the request belongs to the…

Published by the source

7 Oct 2026, 13:59 UTC

Last modified by the source

26 Oct 2026, 16:00 UTC

Source last checked

27 Oct 2026, 06:15 UTC

1. Revision 5 · amended · 27 Oct 2026

   Amended from osv record GHSA-rjpf-7pf5-q54x

2. Revision 4 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-rjpf-7pf5-q54x

3. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-rjpf-7pf5-q54x

4. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-rjpf-7pf5-q54x

5. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-rjpf-7pf5-q54x

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

# Patch Next advisory brief: CVE-2026-46438

Advisory: wger: Cross-User Data Corruption via Missing Ownership Check on WorkoutLog.slot_entry
IDs: CVE-2026-46438, GHSA-rjpf-7pf5-q54x
Record: https://patchnext.com/advisories/cve-2026-46438 (revision 5, source checked 27 Oct 2026, 06:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.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.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://github.com/advisories/GHSA-rjpf-7pf5-q54x (GitHub-reviewed advisory GHSA-rjpf-7pf5-q54x lists affected ranges: PyPI wger >=0 <=2.1)
- Verified: https://osv.dev/vulnerability/GHSA-rjpf-7pf5-q54x (OSV record GHSA-rjpf-7pf5-q54x lists affected ranges: PyPI wger >=0 <=2.1)

Commands are suggestions: review each one before running it.