<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-17T20:30:57.044732+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-27835</id>
    <title>CVE-2026-27835 — wger: IDOR in RepetitionsConfig and MaxRepetitionsConfig API leak other users' workout data</title>
    <updated>2026-11-17T20:30:57.046398+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> wger-project wger</p>
<p>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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-27835"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2026-3423</id>
    <title>PYSEC-2026-3423 — wger: IDOR in RepetitionsConfig and MaxRepetitionsConfig API leak other users' workout data</title>
    <updated>2026-11-17T20:30:57.046476+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: wger</p>
<p>### Summary</p>
<p>`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.</p>
<p>### Details</p>
<p>`wger/manager/api/views.py:499` and `:518`:</p>
<p>```python
# VULNERABLE
class RepetitionsConfigViewSet(viewsets.ModelViewSet):
    def get_queryset(self):
        return RepetitionsConfig.objects.all()</p>
<p>class MaxRepetitionsConfigViewSet(viewsets.ModelViewSet):
    def get_queryset(self):
        return MaxRepetitionsConfig.objects.all()
```</p>
<p>Every sibling viewset in the same file correctly filters by user. For example, `WeightConfigViewSet` at line 459:</p>
<p>```python
# CORRECT — how it should work
def get_queryset(self):
    return WeightConfig.objects.filter(
        slot_entry__slot__day__routine__user=self.request.user
    )
```</p>
<p>The same user filter is present on `SetsConfig`, `RestConfig`, `RiRConfig`, and their Max variants — only `RepetitionsConfig` and `MaxRepetitionsConfig` are missing it.</p>
<p>### PoC</p>
<p>```python
import requests</p>
<p>BASE = "http://localhost"
headers = {"Authorization": "Token YOUR_TOKEN"}  # any registered user</p>
<p>r = requests.get(f"{BASE}/api/v2/repetitions-config/", headers=headers)
print(r.json())  # returns ALL users' repetition configs, not just your own</p>
<p>r = requests.get(f"{BASE}/api/v2/max-repetitions-config/", headers=headers)
print(r.json())  # same — all users' max…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2026-3423"/>
  </entry>
</feed>
