LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27839: wger: IDOR in nutritional_values endpoints exposes private dietary data via direct ORM lookup

wger is a free, open-source workout and fitness manager. In versions up to and including 2.4, three `nutritional_values` 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. Commit 29876a1954fe959e4b58ef070170e81703dab60e contains a fix for the issue.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-27839 is a privacy issue in wger, an open-source fitness manager. Authenticated users could access another user’s private nutrition plan details by guessing or supplying record IDs. Exposed data may include caloric intake and macro breakdowns. This is not a system takeover issue, but it can expose sensitive health and dietary information.

Executive priority

Treat as a moderate privacy issue. Organizations hosting wger for multiple users should remediate promptly because private health-adjacent data may be exposed between accounts. It is less urgent than remote code execution, but important for trust and privacy obligations.

Technical view

wger versions up to and including 2.4 have an IDOR/CWE-639 flaw in three nutritional_values action endpoints. The endpoints use Model.objects.get(pk=pk), bypassing the user-scoped queryset. Any authenticated user can retrieve another user’s nutrition plan data by referencing an arbitrary primary key. The listed fix is commit 29876a1954fe959e4b58ef070170e81703dab60e.

Likely exposure

Exposure is limited to wger deployments on version 2.4 or earlier where users can authenticate. Risk is higher for public or multi-user instances because any authenticated account may access other users’ private dietary records.

Exploitation context

The source bundle does not report active exploitation, and KEV is false. Exploitation requires valid authentication but no user interaction. The impact described is confidentiality-only: private nutrition data disclosure, not modification or service disruption.

Researcher notes

The vulnerability is an authenticated IDOR caused by bypassing user-scoped querysets in nutritional_values action endpoints. Evidence identifies affected versions as up to and including 2.4 and points to a fixing commit. No public source in the bundle confirms exploitation in the wild or a specific patched release number.

Mitigation direction

  • Identify all wger deployments and confirm their versions.
  • Prioritize public or multi-user wger instances.
  • Apply the vendor fix referenced in commit 29876a1954fe959e4b58ef070170e81703dab60e.
  • Check the GitHub advisory for updated release or upgrade guidance.
  • Review access logs for unusual nutritional_values object access patterns.

Validation and detection

  • Confirm wger is not running version 2.4 or earlier.
  • Verify the deployed code no longer uses raw pk lookup in affected endpoints.
  • Confirm nutritional_values access is constrained to the authenticated user’s queryset.
  • Review vendor advisory status before closing the issue.
  • Document whether any exposed instance allowed untrusted user registration.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-27839 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-27839Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
wger-projectwger<= 2.4Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.