# CVE-2026-40474: wger has Broken Access Control in the Global Gym Configuration Update Endpoint

> Authenticated users can modify global gym configuration due to missing permission checks, leading to privilege escalation and bulk profile updates.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Apr 2026
- **Updated:** 20 Apr 2026
- **Also known as:** GHSA-xppv-4jrx-qf8m, PYSEC-2026-3424

## What is CVE-2026-40474?

CVE-2026-40474 is a high-severity missing authorization vulnerability in wger-project wger, published on 17 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

wger is a free, open-source workout and fitness manager. In versions 2.5 and below, the GymConfigUpdateView declares permission_required = 'config.change_gymconfig' but inherits WgerFormMixin instead of WgerPermissionMixin, so the permission is never enforced at runtime. Since GymConfig is an ownerless singleton, any authenticated user can modify the global gym configuration, triggering save() side effects that bulk-update user profile gym assignments — a vertical privilege escalation to installation-wide configuration control. This issue is fixed in version 2.5.

Weakness: CWE-862 (Missing Authorization), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-40474?

3 open source packages ship an affected version, including wger. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wger` | PyPI | All versions to 2.1 | None |
| `wger` | PyPI | All versions to 2.1 | None |
| `wger` | PyPI | All versions to 2.1 | None |

Products: Wger Wger.

## How do I fix CVE-2026-40474?

No fix has been published for CVE-2026-40474 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-40474 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40474 exists.

## Other vulnerabilities in wger-project wger

- [CVE-2022-2650](https://insights.sbomify.com/CVE-2022-2650/): Improper Restriction of Excessive Authentication Attempts in wger-project/wger (high 7.8)
- [CVE-2026-40353](https://insights.sbomify.com/CVE-2026-40353/): wger: Stored XSS via Unescaped License Attribution Fields (medium 5.1)
- [CVE-2026-27835](https://insights.sbomify.com/CVE-2026-27835/): wger: IDOR in RepetitionsConfig and MaxRepetitionsConfig API leak other users' workout data (medium 4.3)
- [CVE-2026-27839](https://insights.sbomify.com/CVE-2026-27839/): wger: IDOR in nutritional_values endpoints exposes private dietary data via direct ORM lookup (medium 4.3)
- [CVE-2026-27838](https://insights.sbomify.com/CVE-2026-27838/): wger: IDOR via user-unscoped cache keys on routine API actions exposes workout data (low 3.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-40474 and fix it if it is affected.

What it is: CVE-2026-40474 is a high-severity missing authorization vulnerability in wger-project wger, published on 17 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40474 exists.

Affected packages and fixed versions:
- wger (PyPI): affected all versions up to 2.1; no fix listed
- wger (PyPI): affected all versions up to 2.1; no fix listed
- wger (PyPI): affected all versions up to 2.1; no fix listed

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-40474/ (Markdown: https://insights.sbomify.com/CVE-2026-40474/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40474
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40474
- OSV: https://osv.dev/vulnerability/CVE-2026-40474

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-40474/
Summaries are generated and may contain mistakes; the official description above is the record.