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

Advisory record · `GHSA-rjpf-7pf5-q54x`

- **Identifiers:** `GHSA-rjpf-7pf5-q54x` · `CVE-2026-46438` · `PYSEC-2026-4314`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-639](https://cwe.mitre.org/data/definitions/639.html) · [CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 7 Oct 2026
- **Updated:** 26 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 7 Oct 2026, 13:59 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `wger` (PyPI): affected `<=2.1`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Wger versions up to and including 2.1 are affected. An authenticated user can create workout log entries that reference another user's slot entry, because the server's ownership check does not cover that field, and the injected entries are then included in the victim's progression calculations. The source describes the attacker needing only a slot entry ID and an account of their own, and says the victim gets no notification. The advisory lists no fixed version, but it proposes adding the slot entry to the ownership check and filtering logs by routine owner.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0023, the 13th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:07 UTC: First seen by agentprime
- 31 Oct 2026, 14:07 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-rjpf-7pf5-q54x)

## Sources

- [GitHub Advisory Database: GHSA-rjpf-7pf5-q54x](https://github.com/advisories/GHSA-rjpf-7pf5-q54x)
- [OSV: GHSA-rjpf-7pf5-q54x](https://osv.dev/vulnerability/GHSA-rjpf-7pf5-q54x)
- <https://github.com/wger-project/wger/security/advisories/GHSA-rjpf-7pf5-q54x>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-46438>
- <https://github.com/wger-project/wger/commit/b29cf178651bbcc243d21673932e32bd42017893>
- <https://github.com/pypa/advisory-database/tree/main/vulns/wger/PYSEC-2026-4314.yaml>
- <https://github.com/wger-project/wger>
- <https://github.com/wger-project/wger/releases/tag/2.6>
- <https://pypi.org/project/wger>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-rjpf-7pf5-q54x>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-rjpf-7pf5-q54x/>. Everything for agents: <https://agentprime.io/llms.txt>.