dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-7049

HIGH · 8.8 CVSS v3.1 Published 2025-09-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 privilege escalation in all versions up to, and including, 67.7.0 via the 'MJ_gmgt_gmgt_add_user' function due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to change the email, password, and other details of any user, including Administrator users.

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 WordPress plugin has a privilege escalation vulnerability in the 'MJ_gmgt_gmgt_add_user' function. Due to missing validation on a user-controlled key, authenticated users with minimal Subscriber-level access can modify email addresses, passwords, and other details of any user account including Administrators, effectively allowing full privilege escalation.

MitigationUpdate the WPGYM plugin to a version beyond 67.7.0. If no patched version is available, disable the plugin immediately and review user accounts for unauthorized changes.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Identify if WPGYM plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WPGYM' or 'Gym Management' plugin, or inspect the wp-content/plugins/ directory for the plugin folder
    Affected if WPGYM or Gym Management plugin is present in the WordPress installation
  2. Check installed WPGYM plugin version
    In WordPress admin > Plugins, click 'View Details' on the WPGYM plugin to see the version number, or open the main plugin PHP file and read the Version header in the plugin comments
    Affected if Installed version is 67.7.0 or earlier (versions beyond 67.7.0 contain the fix)
  3. Audit WordPress user accounts for unauthorized changes
    Navigate to Users > All Users in WordPress admin and look for unexpected Administrator accounts, or directly query the wp_users and wp_usermeta tables to check for sudden role changes or new admin accounts created by lower-privileged users
    Affected if Administrator accounts exist that were not created by existing admins, or Subscriber-level users have been elevated to Administrator without authorization

Environment is affected if WPGYM plugin version is 67.7.0 or earlier AND unauthorized privilege escalation changes are found in user accounts.

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

Update the WPGYM plugin to a version beyond 67.7.0. If no patched version is available, disable the plugin immediately and review user accounts for unauthorized changes.

Recommended fix Moderate confidence

Version 67.7.1 or later (any version higher than 67.7.0)

  1. Check current installed version of the WPGYM - WordPress Gym Management System plugin
  2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. If a newer version is available, click 'Update Now' to upgrade the plugin
  4. Alternatively, download the latest version from the official source (CodeCanyon) and upload via Plugins > Add New > Upload Plugin
  5. After updating, verify that the 'MJ_gmgt_gmgt_add_user' function has been patched and no longer allows subscriber-level users to modify other users' credentials

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7049 — 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-7049 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