{"answers":{"affected":"3 open source packages ship an affected version, including wger.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46438 exists.","fix":"No fix has been published for CVE-2026-46438 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-46438 is a medium-severity missing authorization vulnerability in wger-project wger, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-46438 and fix it if it is affected.\n\nWhat it is: CVE-2026-46438 is a medium-severity missing authorization vulnerability in wger-project wger, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46438 exists.\n\nAffected packages and fixed versions:\n- wger (PyPI): affected all versions up to 2.1; no fix listed\n- wger (PyPI): affected all versions up to 2.1; no fix listed\n- wger (PyPI): affected all versions up to 2.1; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-46438/ (Markdown: https://insights.sbomify.com/CVE-2026-46438/index.md)","id":"CVE-2026-46438","markdown":"https://insights.sbomify.com/CVE-2026-46438/index.md","name":"CVE-2026-46438","record":{"aliases":["GHSA-rjpf-7pf5-q54x","PYSEC-2026-4314"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"wger fitness manager","requires_auth":"low_privilege","summary":"An authenticated attacker can inject arbitrary workout log entries into other users' profiles, corrupting their training data calculations.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"wger is a free, open-source workout and fitness manager. Prior to version 2.6, an authenticated attacker can inject arbitrary workout log entries into any other user's `SlotEntry` by supplying the victim's `slot_entry` ID in a `POST /api/v2/workoutlog/` request. The `slot_entry` foreign key is not included in the ownership verification performed by `WorkoutLogViewSet.get_owner_objects()`, so the server accepts and persists the cross-user reference without error. Because `SlotEntry.get_config_data()` retrieves associated logs via `self.workoutlog_set.all()` with no user filter, the attacker's injected data is silently folded into the victim's progressive-overload calculations, corrupting their auto-generated weight and repetition targets. Version 2.6 contains a patch.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"wger: Cross-User Data Corruption via Missing Ownership Check on WorkoutLog.slot_entry","id":"CVE-2026-46438","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"compliance-trestle Vulnerable to Remote Code Execution via Recursive Server-Side Template Injection (SSTI)","id":"CVE-2026-46439"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.1"],"package":"wger","purl":null,"source":"GHSA-rjpf-7pf5-q54x"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.1"],"package":"wger","purl":"pkg:pypi/wger","source":"GHSA-rjpf-7pf5-q54x"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.1"],"package":"wger","purl":"pkg:pypi/wger","source":"PYSEC-2026-4314"}],"prev":{"headline":"wger: API credentials remain valid after logout/password change","id":"CVE-2026-46437"},"products":["wger"],"published":"2026-10-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-07","vendors":["wger-project"]},"summary":"An authenticated attacker can inject arbitrary workout log entries into other users' profiles, corrupting their training data calculations.","url":"https://insights.sbomify.com/CVE-2026-46438/"}