# CVE-2026-27835: wger: IDOR in RepetitionsConfig and MaxRepetitionsConfig API leak other users' workout data

> Attackers can view other users' workout data due to missing authorization checks in API endpoints.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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:** 26 Feb 2026
- **Updated:** 3 Mar 2026
- **Also known as:** GHSA-xf68-8hjw-7mpm, PYSEC-2026-3423

## What is CVE-2026-27835?

CVE-2026-27835 is a medium-severity missing authorization vulnerability in wger-project wger, published on 26 Feb 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. In versions up to and including 2.4, `RepetitionsConfigViewSet` and `MaxRepetitionsConfigViewSet` return all users' repetition config data because their `get_queryset()` calls `.all()` instead of filtering by the authenticated user. Any registered user can enumerate every other user's workout structure. Commit 1fda5690b35706bb137850c8a084ec6a13317b64 contains a fix for the issue.

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

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

3 open source packages ship an affected version, including wger. It affects 1 product.


| 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 |

Products: Wger Wger.

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

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

## Is CVE-2026-27835 being exploited?

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

## Other vulnerabilities in wger-project wger

- [CVE-2022-2650](https://insights.sbomify.com/CVE-2022-2650/): Improper Restriction of Excessive Authentication Attempts in wger-project/wger (high 7.8)
- [CVE-2026-40474](https://insights.sbomify.com/CVE-2026-40474/): wger has Broken Access Control in the Global Gym Configuration Update Endpoint (high 7.6)
- [CVE-2026-40353](https://insights.sbomify.com/CVE-2026-40353/): wger: Stored XSS via Unescaped License Attribution Fields (medium 5.1)
- [CVE-2026-27839](https://insights.sbomify.com/CVE-2026-27839/): wger: IDOR in nutritional_values endpoints exposes private dietary data via direct ORM lookup (medium 4.3)
- [CVE-2026-27838](https://insights.sbomify.com/CVE-2026-27838/): wger: IDOR via user-unscoped cache keys on routine API actions exposes workout data (low 3.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-27835 is a medium-severity missing authorization vulnerability in wger-project wger, published on 26 Feb 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-27835 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-27835/ (Markdown: https://insights.sbomify.com/CVE-2026-27835/index.md)
```

## Sources

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

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