Security readout for executives and security teams
Plain-English summary
CVE-2026-27835 is an access-control flaw in wger, an open-source fitness manager. Any registered user could view other users’ repetition configuration data through affected API endpoints. This exposes workout structure information but does not indicate data modification or service disruption. The issue affects wger versions up to and including 2.4.
Executive priority
Treat as a privacy and tenant-data separation issue. Prioritize remediation for internet-accessible or multi-user wger deployments, especially where workout data is considered sensitive. Business impact is moderate because exploitation requires a registered account and affects confidentiality only, per the supplied CVSS.
Technical view
The flaw is CWE-639, an insecure direct object reference. RepetitionsConfigViewSet and MaxRepetitionsConfigViewSet used get_queryset() with .all(), returning repetition configuration records for all users instead of filtering by the authenticated user. CVSS is 4.3: network-accessible, low complexity, authenticated access required, confidentiality impact only.
Likely exposure
Exposure is limited to deployments of wger version 2.4 or earlier with registered users able to access the affected APIs. The data exposed is other users’ repetition configuration and workout structure, not full account takeover based on provided sources.
Exploitation context
The advisory indicates any registered user can enumerate other users’ workout structure through the vulnerable API behavior. There is no provided evidence of active exploitation, and the CVE is not listed as KEV in the supplied data.
Researcher notes
Evidence is limited to the CVE data, GitHub advisory, and fix commit. The core issue is improper queryset scoping in two API viewsets. Do not assume broader user data exposure beyond repetition configuration data unless confirmed by code review or vendor guidance.
Mitigation direction
- Upgrade to a fixed wger release if available from the project.
- Apply or verify the fix in commit 1fda5690b35706bb137850c8a084ec6a13317b64.
- Review the GitHub advisory for current vendor guidance.
- Restrict registration or API access where practical until remediated.
Validation and detection
- Inventory wger deployments and identify versions up to and including 2.4.
- Confirm the affected viewsets filter results by authenticated user.
- Review API access logs for unusual authenticated enumeration patterns.
- Validate remediation against the referenced fixed commit or vendor release notes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2026-27835 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/wger-project/wger/security/advisories/GHSA-xf68-8hjw-7mpmCVE reference · x_refsource_CONFIRM
- https://github.com/wger-project/wger/commit/1fda5690b35706bb137850c8a084ec6a13317b64CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.