Wordpress Gym Management SystemWordPress extension · Mojoomla
CVE-2024-9942
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 · uneditedThe WPGYM - Wordpress Gym Management System plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the MJ_gmgt_user_avatar_image_upload() function in all versions up to, and including, 67.1.0. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.
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 confidenceThe WPGYM WordPress plugin has an arbitrary file upload vulnerability in the MJ_gmgt_user_avatar_image_upload() function due to missing file type validation, allowing unauthenticated attackers to upload arbitrary files that could achieve remote code execution.
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
Wordpress Gym Management SystemWordPress extension
< 67.2.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm WPGYM plugin installationCheck WordPress plugins directory (wp-content/plugins/) for directories containing 'gym', 'gym-management', or 'mojoomla', or list installed plugins via WordPress admin or wp-cli command: wp plugin list --status=activeAffected if The Mojoomla Wordpress Gym Management System plugin is found installed on the WordPress site
-
Identify installed plugin versionRead the main plugin PHP file header for version number, or check plugin changelog/readme file, or use: wp plugin get gym-management-system --format=jsonAffected if Version is less than 67.2.0 (versions below this version lack proper file type validation)
-
Verify upload function accessibilityCheck if the file upload endpoint exists by inspecting plugin source code for MJ_gmgt_user_avatar_image_upload function calls and corresponding AJAX actions or form handlersAffected if The upload functionality is present and reachable (function exists in the plugin code)
-
Inspect upload directories for suspicious filesSearch wp-content/uploads/ and subdirectories (especially avatar/user folders) for unexpected file extensions like .php, .phtml, .js, or .exe that were uploaded outside normal avatar image formatsAffected if Unexpected executable or script files are found in upload directories, indicating potential exploitation
The environment is affected if the Mojoomla Wordpress Gym Management System plugin is installed with a version lower than 67.2.0 and the upload functionality is accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scoped67.2.0
Update the plugin to version 67.1.1 or later which includes proper file type validation, or disable the plugin until a patch can be applied.
67.2.0
- Backup your WordPress site and database before making any changes
- Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
- Find the 'WPGYM - Wordpress Gym Management System' plugin
- Click 'Update now' if an update is available, or manually upload version 67.2.0 or later from the vendor (codecanyon.net)
- Verify the plugin is running version 67.2.0 or higher after updating
- Test the avatar upload functionality to confirm the file type validation is working
- Monitor site for any unusual activity following the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wordpress Gym Management System
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9942 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-9942 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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