# CVE-2026-82544: wger-project wger Password Reset gym.py reset_user_password cross-site request forgery

> Attackers can perform cross-site request forgery on the password reset function, potentially taking over user accounts in the wger fitness application.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-frcw-fw5q-gh4g

## What is CVE-2026-82544?

CVE-2026-82544 is a medium-severity vulnerability in wger-project wger, published on 30 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A flaw has been found in wger-project wger up to 2.6.0-alpha2. This issue affects the function reset_user_password of the file wger/gym/views/gym.py of the component Password Reset. Executing a manipulation can lead to cross-site request forgery. It is possible to launch the attack remotely. This patch is called 3c6ce4b7f3eeafeb35318c6c4e82b1a3fd28b314. It is advisable to implement a patch to correct this issue.

Weakness: CWE-862 (Missing Authorization), CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-82544 being exploited?

There is no known exploitation of CVE-2026-82544 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82544 is a medium-severity vulnerability in wger-project wger, published on 30 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-82544 in the wild and no public exploit code.

Affected product: wger-project wger. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-82544/ (Markdown: https://insights.sbomify.com/CVE-2026-82544/index.md)
```

## Sources

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

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