# CVE-2026-43977: wger IDOR: Authenticated Users Can Read Others' Private Workout Session Data via Template Routine API

> Authenticated attackers can read other users' private workout data by accessing template routines, exposing sensitive training history.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-cj9g-27ph-4cgv, PYSEC-2026-3421

## What is CVE-2026-43977?

CVE-2026-43977 is a high-severity missing authorization vulnerability in wger-project wger, published on 16 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

wger is a free, open-source workout and fitness manager. In versions prior to 2.6, any authenticated user can read another user's private workout session notes, exercise history, and training statistics by calling the /logs/ and /stats/ actions on a routine they do not own. The vulnerability exists in RoutineViewSet (wger/manager/api/views.py). The view defines two custom actions /logs/ and /stats/ that are intended to return data for the requesting user's own training history within a routine. However, the underlying permission check (RoutinePermission.has_object_permission) grants read access to any authenticated user when the routine has is_template=True, regardless of ownership. When the /logs/ or /stats/ actions are invoked against a routine the attacker does not own, they return the owner's private workout history, not the attacker's. This issue has been fixed in version 2.6.

Weakness: CWE-863 (Incorrect Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

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

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


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

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

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

## Is CVE-2026-43977 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-43977 is a high-severity missing authorization vulnerability in wger-project wger, published on 16 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-43977 exists.

Affected packages and fixed versions:
- wger (PyPI): affected all versions up to 2.5; no fix listed
- wger (PyPI): affected all versions up to 2.5; no fix listed
- wger (PyPI): affected all versions up to 2.5; 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-43977/ (Markdown: https://insights.sbomify.com/CVE-2026-43977/index.md)
```

## Sources

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

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