wger-project wger up to 2.4 self.get_object authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.2 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in wger-project wger up to 2.4. This affects the function self.get_object. The manipulation results in authorization.
This vulnerability was named CVE-2026-27838. The attack may be performed from remote. There is no available exploit.
It is advisable to implement a patch to correct this issue.
Details
A vulnerability was found in wger-project wger up to 2.4. It has been classified as problematic. Affected is the function self.get_object. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality. CVE summarizes:
wger is a free, open-source workout and fitness manager. Five routine detail action endpoints check a cache before calling `self.get_object()`. In versions up to and including 2.4, ache keys are scoped only by `pk` — no user ID is included. When a victim has previously accessed their routine via the API, an attacker can retrieve the cached response for the same PK without any ownership check. Commit e964328784e2ee2830a1991d69fadbce86ac9fbf contains a patch for the issue.
The advisory is shared for download at github.com. This vulnerability is traded as CVE-2026-27838 since 02/24/2026. The exploitability is told to be difficult. It is possible to launch the attack remotely. There are known technical details, but no exploit is available.
Applying the patch e964328784e2ee2830a1991d69fadbce86ac9fbf is able to eliminate this problem. The bugfix is ready for download at github.com.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.2VulDB Meta Temp Score: 3.2
VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 3.5
NVD Vector: 🔒
CNA Base Score: 3.1
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-639 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔒
Patch: e964328784e2ee2830a1991d69fadbce86ac9fbf
Timeline
02/24/2026 CVE reserved02/27/2026 Advisory disclosed
02/27/2026 VulDB entry created
03/03/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-42cr-w2gr-m54q
Status: Confirmed
CVE: CVE-2026-27838 (🔒)
GCVE (CVE): GCVE-0-2026-27838
GCVE (VulDB): GCVE-100-348108
Entry
Created: 02/27/2026 07:54Updated: 03/03/2026 12:17
Changes: 02/27/2026 07:54 (66), 03/03/2026 12:17 (12)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.