wger-project wger up to 2.5 Ownership Verification /api/v2/workoutlog WorkoutLogViewSet.get_owner_objects slot_entry authorization

Summaryinfo

A vulnerability classified as problematic has been found in wger-project wger up to 2.5. This issue affects the function WorkoutLogViewSet.get_owner_objects of the file /api/v2/workoutlog of the component Ownership Verification. The manipulation of the argument slot_entry leads to authorization. This vulnerability is documented as CVE-2026-46438. The attack can be initiated remotely. There is not any exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in wger-project wger up to 2.5. This issue affects the function WorkoutLogViewSet.get_owner_objects of the file /api/v2/workoutlog of the component Ownership Verification. The manipulation of the argument slot_entry with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. Impacted is integrity. The summary by CVE is:

wger is a free, open-source workout and fitness manager. Prior to version 2.6, an authenticated attacker can inject arbitrary workout log entries into any other user's `SlotEntry` by supplying the victim's `slot_entry` ID in a `POST /api/v2/workoutlog/` request. The `slot_entry` foreign key is not included in the ownership verification performed by `WorkoutLogViewSet.get_owner_objects()`, so the server accepts and persists the cross-user reference without error. Because `SlotEntry.get_config_data()` retrieves associated logs via `self.workoutlog_set.all()` with no user filter, the attacker's injected data is silently folded into the victim's progressive-overload calculations, corrupting their auto-generated weight and repetition targets. Version 2.6 contains a patch.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-46438 since 05/14/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available.

Upgrading to version 2.6 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Project Management Software

Vendor

• wger-project

Name

• wger

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5

Website

• Product: https://github.com/wger-project/wger/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion