# CVE-2026-46438: wger: Cross-User Data Corruption via Missing Ownership Check on WorkoutLog.slot_entry

> An authenticated attacker can inject arbitrary workout log entries into other users' profiles, corrupting their training data calculations.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-rjpf-7pf5-q54x, PYSEC-2026-4314

## What is CVE-2026-46438?

CVE-2026-46438 is a medium-severity missing authorization vulnerability in wger-project wger, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

wger is a free, open-source workout and fitness manager. Prior to version 2.6, 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. Version 2.6 contains a patch.

Weakness: CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-46438?

3 open source packages ship an affected version, including wger.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wger` | PyPI | All versions to 2.1 | None |
| `wger` | PyPI | All versions to 2.1 | None |
| `wger` | PyPI | All versions to 2.1 | None |

## How do I fix CVE-2026-46438?

No fix has been published for CVE-2026-46438 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-46438 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46438 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46438 and fix it if it is affected.

What it is: CVE-2026-46438 is a medium-severity missing authorization vulnerability in wger-project wger, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46438 exists.

Affected packages and fixed versions:
- wger (PyPI): affected all versions up to 2.1; no fix listed
- wger (PyPI): affected all versions up to 2.1; no fix listed
- wger (PyPI): affected all versions up to 2.1; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46438/ (Markdown: https://insights.sbomify.com/CVE-2026-46438/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46438
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46438
- OSV: https://osv.dev/vulnerability/CVE-2026-46438

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46438/
Summaries are generated and may contain mistakes; the official description above is the record.