🛡️ CVE-2026-27835 — wger

🟡 CVSS 4.3 — Medium ⚠️ Exploit Public CWE-639 OSV
4.3
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

wger: IDOR in RepetitionsConfig and MaxRepetitionsConfig API leak other users' workout data

Summary

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.

Details

wger/manager/api/views.py:499 and :518:

```python

# VULNERABLE

class RepetitionsConfigViewSet(viewsets.ModelViewSet):

def get_queryset(self):

return RepetitionsConfig.objects.all()

class MaxRepetitionsConfigViewSet(viewsets.ModelViewSet):

def get_queryset(self):

return MaxRepetitionsConfig.objects.all()

```

Every sibling viewset in the same file correctly filters by user. For example, WeightConfigViewSet at line 459:

```python

# CORRECT — how it should work

def get_queryset(self):

return WeightConfig.objects.filter(

slot_entry__slot__day__routine__user=self.request.user

)

```

The same user filter is present on SetsConfig, RestConfig, RiRConfig, and their Max variants — only RepetitionsConfig and MaxRepetitionsConfig are missing it.

PoC

```python

import requests

BASE = "http://localhost"

headers = {"Authorization": "Token YOUR_TOKEN"} # any registered user

r = requests.get(f"{BASE}/api/v2/repetitions-config/", headers=headers)

print(r.json()) # returns ALL users' repetition configs, not just your own

r = requests.get(f"{BASE}/api/v2/max-repetitions-config/", headers=headers)

print(r.json()) # same — all users' max repetition configs

```

Registration is open by default. Sequential IDs allow full enumeration.

Impact

Any authenticated user can read other users' repetition and max-repetitions configs, exposing workout structure (slot entry IDs, iteration values, operations, step counts, repeat flags, requirements JSON). This is a broken object-level authorization (BOLA/IDOR) vulnerability — the same class of issue as OWASP API1.

Fix: Add the same user filter used by every other config viewset:

```python

def get_queryset(self):

return RepetitionsConfig.objects.filter(

slot_entry__slot__day__routine__user=self.request.user

)

```

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality low, integrity none, availability none.

Weakness class

CVE-2026-27835 is classified as CWE-639: Authorization Bypass Through User-Controlled Key. An object is selected by an identifier from the request without checking the caller owns it.

Affected software

CVE-2026-27835 is recorded against 1 package.

  • wger

Timeline and source

Published on 26 February 2026 and last revised on 13 July 2026. A public exploit is known to exist, which raises the urgency of patching considerably. A vendor advisory or fix has been published. Record sourced from OSV.

References

github.com (Web)
nvd.nist.gov (Advisory)
github.com (Web)
github.com (Package)

Details

Severity MEDIUM
CVSS Score 4.3
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
CWE CWE-639
Public Exploit ⚠️ Yes
Source OSV
Published 2026-02-26
Updated 2026-08-12
Modified 2026-07-13

Affected Packages

Software From version Fixed in
wger

Similar Threats

Exploit Protection

Are you running wger?

CVE-2026-27835 carries CVSS 4.3 Medium rating and a public exploit already exists. BotEraser checks your installation against this and other known CVE records, and blocks IPs associated with exploit activity.

Check My Site For CVE-2026-27835 →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2026