dbcve.org
Workout ManagerApplication · Wger

CVE-2023-38759

HIGH · 8.8 CVSS v3.1 Published 2023-08-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross Site Request Forgery (CSRF) vulnerability in wger Project wger Workout Manager 2.2.0a3 allows a remote attacker to gain privileges via the user-management feature in the gym/views/gym.py, templates/gym/reset_user_password.html, templates/user/overview.html, core/views/user.py, and templates/user/preferences.html, core/forms.py components.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cross Site Request Forgery (CSRF) vulnerability in wger Workout Manager 2.2.0a3 allows remote attackers to perform unauthorized actions via the user-management functionality in gym/views/gym.py, core/views/user.py, and associated templates (reset_user_password.html, overview.html, preferences.html) and core/forms.py. The affected components lack proper CSRF token validation on state-changing forms.

MitigationImplement anti-CSRF tokens (e.g., Django's {% csrf_token %}) on all user-management forms and ensure corresponding views use @csrf_protect decorator or csrf_exempt is not improperly applied; also configure SameSite cookie attributes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Workout ManagerApplication
Affected:= 2.2.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Wger Workout Manager version
    Locate the version file or check the application header/admin interface for the version number. Common locations: version.py, __init__.py in the main package, or the admin dashboard.
    Affected if The installed version is exactly 2.2.0 (the only affected version listed).
  2. Inspect reset_user_password.html template for CSRF token
    Open the template file (typically in templates/ directory) and search for '{% csrf_token %}' inside the <form> tag. This template handles password reset functionality.
    Affected if The template does NOT contain '{% csrf_token %}' within the password reset form tags.
  3. Inspect overview.html template for CSRF token
    Open the user overview template and locate all <form> elements. Verify whether each form that performs a state-changing action includes '{% csrf_token %}'.
    Affected if The overview template contains state-changing forms (such as user activation/deactivation) that are missing the csrf_token tag.
  4. Inspect preferences.html template for CSRF token
    Open the user preferences template and check all <form> tags for the presence of '{% csrf_token %}'. Look for forms handling preference updates.
    Affected if The preferences form lacks '{% csrf_token %}' inside the form tags.
  5. Verify gym.py views have CSRF protection
    Open gym/views/gym.py and examine the view functions that handle user management (state-changing operations). Check for @csrf_protect decorator or ensure @csrf_exempt is not applied to these views.
    Affected if The gym management views lack @csrf_protect decorator or incorrectly have @csrf_exempt applied.
  6. Verify user.py views have CSRF protection
    Open core/views/user.py and examine views handling user-related state changes. Check for proper CSRF decorator usage.
    Affected if The user management views are missing @csrf_protect decorator or have @csrf_exempt improperly applied.

You are affected if you run Wger Workout Manager version 2.2.0 AND any of the user-management templates (reset_user_password.html, overview.html, preferences.html) are missing {% csrf_token %} in their forms, OR the corresponding views in gym/views/gym.py or core/views/user.py lack proper CSRF protection decorators.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (e.g., Django's {% csrf_token %}) on all user-management forms and ensure corresponding views use @csrf_protect decorator or csrf_exempt is not improperly applied; also configure SameSite cookie attributes.

Recommended fix Moderate confidence

Upgrade to wger Workout Manager 2.2.0 stable release or later

  1. 1. Identify the current wger Workout Manager version in use by checking the application's version file or admin interface
  2. 2. Navigate to the official wger GitHub repository at github.com/wger-project/wger to identify the latest stable release
  3. 3. Review the release notes or commit history to confirm a fix for CVE-2023-38759 (CSRF vulnerability in user-management components)
  4. 4. Create a backup of the current application database and configuration files
  5. 5. Upgrade the wger Workout Manager installation to version 2.2.0 stable or a later release that includes the security fix
  6. 6. Verify the upgrade was successful by checking the application version
  7. 7. Test user management features (user creation, password reset, preferences) to confirm functionality
  8. 8. Validate that CSRF protections are properly implemented in the affected components: gym/views/gym.py, core/views/user.py, and associated templates
Caveat Minor: Review release notes for any configuration changes in user management or template modifications that may require template updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Workout Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-38759 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-38759 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data