dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-7442

HIGH · 7.5 CVSS v3.1 Published 2025-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
The WPGYM - Wordpress Gym Management System plugin for WordPress is vulnerable to SQL Injection via several parameters in the MJ_gmgt_delete_class_limit_for_member, MJ_gmgt_get_yearly_income_expense, MJ_gmgt_get_monthly_income_expense, MJ_gmgt_add_class_limit, MJ_gmgt_view_meeting_detail, and MJ_gmgt_create_meeting functions in all versions up to 67.8.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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

The WPGYM plugin for WordPress is vulnerable to unauthenticated SQL injection in six different functions (MJ_gmgt_delete_class_limit_for_member, MJ_gmgt_get_yearly_income_expense, MJ_gmgt_get_monthly_income_expense, MJ_gmgt_add_class_limit, MJ_gmgt_view_meeting_detail, and MJ_gmgt_create_meeting) due to insufficient user input escaping and lack of prepared SQL statements, allowing attackers to inject arbitrary SQL queries.

MitigationUpdate to version 67.8.1 or later if available; otherwise, disable the plugin until a patch is released. Consider implementing Web Application Firewall rules as a temporary mitigation.

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

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 if WPGYM plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Gym Management' or 'WPGYM' in the list. Alternatively, check the wp-content/plugins/ directory for a folder named 'gym-management' or similar.
    Affected if The plugin is installed and active
  2. Get the installed WPGYM version number
    In WordPress admin, go to Plugins > Installed Plugins, find the Gym Management plugin, and note the version number displayed below the plugin name. Alternatively, open the main plugin PHP file (e.g., gym-management/gym-management.php) and look for the 'Version' header in the plugin comments.
    Affected if The version is lower than 67.8.1 or the version number cannot be determined (older unversioned releases)
  3. Verify vulnerable functions exist in the plugin code
    Access the WordPress site files via FTP or file manager. In the plugin directory (wp-content/plugins/gym-management/), search for the function names: MJ_gmgt_delete_class_limit_for_member, MJ_gmgt_get_yearly_income_expense, MJ_gmgt_get_monthly_income_expense, MJ_gmgt_add_class_limit, MJ_gmgt_view_meeting_detail, and MJ_gmgt_create_meeting. Use grep or search through PHP files.
    Affected if Any of these six functions exist in the plugin code (they are vulnerable versions)
  4. Check if AJAX actions are accessible to unauthenticated users
    In the plugin main file, look for add_action('wp_ajax_...') and add_action('wp_ajax_nopriv_...') calls. If wp_ajax_nopriv_ hooks are registered for any of the vulnerable functions, they are accessible without authentication.
    Affected if The vulnerable functions are hooked to wp_ajax_nopriv_ actions, making them exploitable without authentication

You are affected if the WPGYM plugin is installed with a version lower than 67.8.1 and the vulnerable SQL injection functions are present and accessible to unauthenticated users.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 67.8.1 or later if available; otherwise, disable the plugin until a patch is released. Consider implementing Web Application Firewall rules as a temporary mitigation.

Have this fixed 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-2025-7442 — 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-2025-7442 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