wger: IDOR in nutritional_values endpoints exposes private dietary data via direct ORM lookup

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2026-27839: 0.30% estimated exploitation activity in the next 30 days; percentile 23.28 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Three nutritionalvalues action endpoints fetch objects via Model.objects.get(pk=pk) — a raw ORM call that bypasses the user-scoped queryset. Any authenticated user can read another user's private nutrition plan data, including caloric intake and full macro breakdown, by supplying an arbitrary PK. Details DRF detail actions do not automatically apply queryset filtering — the action must call self.getobject() to enforce object-level permissions. These three endpoints skip that and go directly to the ORM: wger/nutrition/api/views.py: The correct pattern used in the same file at LogItemViewSet (line 438): Affected endpoints: PoC No interaction from the victim required. Registration is open by default. PKs are sequential integers. Impact Any authenticated user can read other users' private dietary and health data: - Daily caloric intake - Protein, carbohydrate, fat, fiber, and sodium intake - Full meal composition and ingredient quantities This data is sensitive health information…

Published by the source

26 Feb 2026, 22:15 UTC

Last modified by the source

13 Jul 2026, 16:43 UTC

Source last checked

26 Oct 2026, 13:36 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-g8gc-6c4h-jg86

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-g8gc-6c4h-jg86

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-27839

Advisory: wger: IDOR in nutritional_values endpoints exposes private dietary data via direct ORM lookup
IDs: CVE-2026-27839, GHSA-g8gc-6c4h-jg86
Record: https://patchnext.com/advisories/cve-2026-27839 (revision 2, source checked 26 Oct 2026, 13:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI wger: affected <= 2.1

## Suggested inspection (read-only)
- `python -m pip show wger`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on wger.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-g8gc-6c4h-jg86 (OSV record GHSA-g8gc-6c4h-jg86 lists affected ranges: PyPI wger >=0 <=2.1)
- Verified: https://github.com/advisories/GHSA-g8gc-6c4h-jg86 (GitHub-reviewed advisory GHSA-g8gc-6c4h-jg86 lists affected ranges: PyPI wger >=0 <=2.1)

Commands are suggestions: review each one before running it.