CVE-2025-6080
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 unauthorized admin account creation in all versions up to, and including, 67.7.0. This is due to the plugin not properly validating a user's capabilities prior to adding users. This makes it possible for authenticated attackers, with Subscriber-level access and above, to create new users, including admins.
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 fails to validate user capabilities before performing user creation operations, allowing any authenticated user with Subscriber-level access to create administrative accounts. This privilege escalation vulnerability exists in all versions up to 67.7.0 due to missing authorization checks on user management functions.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm WPGYM plugin installation and versionNavigate to WordPress admin dashboard > Plugins, locate the WPGYM plugin, and note the installed version number. Alternatively, check the plugin header in wp-content/plugins/wpgym/main.php for the Version field.Affected if The installed version is 67.7.0 or any earlier version.
-
Audit user accounts for unauthorized administratorsGo to WordPress admin > Users and review all accounts with Administrator role. Check for accounts you did not create, especially those with suspicious usernames or email addresses that coincide with the time period the plugin was active.Affected if There are admin accounts you did not create, particularly created while the WPGYM plugin was installed.
-
Review user creation capability assignmentCheck if the WPGYM plugin has created any custom roles or modified subscriber capabilities. Use a user role editor plugin or query the wp_options table for modified role capabilities related to wpgym.Affected if Subscriber-level users have been granted elevated capabilities beyond their default permissions.
-
Inspect server access logs for user creation requestsReview web server access logs (Apache/nginx) for POST requests to /wp-admin/admin-ajax.php or custom WPGYM user creation endpoints originating from low-privilege user sessions.Affected if POST requests to user creation endpoints were made by users with subscriber-level authentication.
You are affected if the WPGYM plugin version is 67.7.0 or earlier and unauthorized administrator accounts exist or subscriber-level users have elevated capabilities.
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.
From vendor dataUpdate the WPGYM plugin to a patched version beyond 67.7.0 that implements proper capability checks (manage_options) on all user creation endpoints, and audit existing admin accounts for unauthorized additions.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6080 — 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-2025-6080 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