Submit #857934: wger-project wger 2.6.0-alpha2 / master branch at commit ea7844731f7e3fe5865c327c1f93f5f4a76dde75 CWE-352 Cross-Site Request Forgery / CWE-749 Exposed Dangerous Minfo

Titlewger-project wger 2.6.0-alpha2 / master branch at commit ea7844731f7e3fe5865c327c1f93f5f4a76dde75 CWE-352 Cross-Site Request Forgery / CWE-749 Exposed Dangerous M
Descriptionwger's account deactivation view performs a security-sensitive account action through GET. `UserDeactivateView` inherits from Django's `RedirectView`, and its `get_redirect_url()` method loads the selected user, sets `is_active = False`, saves the user, and redirects. The existing authentication and gym-scope checks limit who can perform the operation, but they do not protect the request from cross-site triggering because GET requests are not CSRF-protected. An attacker can cause an authenticated gym admin, manager, or trainer with sufficient scope to visit a crafted deactivation URL, disabling the target account without the operator's intentional action. Remediation should move deactivation to a POST-only view with CSRF validation and an explicit confirmation step; the sibling activation view should be fixed in the same way.
Source⚠️ https://github.com/wger-project/wger/issues/2380
User
 GalaxynC (UID 98975)
Submission06/13/2026 13:11 (1 month ago)
Moderation07/18/2026 10:37 (1 month later)
StatusDuplicate
VulDB entry236497 [wger Workout Manager 2.2.0a3 User-Management Page gym/views/gym.py cross-site request forgery]
Points0

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!