dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-3671

HIGH · 8.8 CVSS v3.1 Published 2025-08-16
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 Local File Inclusion in all versions up to, and including, 67.7.0 via the 'page' parameter. This makes it possible for authenticated attackers, with Subscriber-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included. The Local File Inclusion exploit can be chained to include various dashboard view files in the plugin. One in particular reported by the researcher can be leveraged to update the password of Super Administrator accounts in Multisite environments making privilege escalation 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 confidence

The WPGYM plugin for WordPress is vulnerable to Local File Inclusion (LFI) via the 'page' parameter in all versions up to 67.7.0. Authenticated attackers with Subscriber-level access or higher can include and execute arbitrary files on the server, allowing execution of any PHP code. The vulnerability can be chained to include dashboard view files and, notably, can update Super Administrator passwords in Multisite environments, enabling privilege escalation.

MitigationImmediately update the WPGYM plugin to the latest version once available. If an update is not available, disable the plugin entirely. Additionally, restrict user permissions to the minimum required and monitor for any suspicious file inclusion activity.

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. Verify WPGYM plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named wpgym or similar. Check if the plugin appears in the list.
    Affected if The WPGYM plugin is present and active in the WordPress installation.
  2. Identify installed WPGYM version
    In WordPress admin, go to Plugins > Installed Plugins and locate WPGYM. The version number is displayed below the plugin name. Alternatively, check the main plugin file (usually wpgym.php) in /wp-content/plugins/wpgym/ for the 'Version' header comment.
    Affected if The installed version is 67.7.0 or any earlier version (versions up to and including 67.7.0 are affected).
  3. Confirm WordPress user roles exist
    Navigate to Users > All Users in WordPress admin. Review the list to see if any users with Subscriber, Contributor, Author, Editor, or Administrator roles exist. The vulnerability requires authenticated access with Subscriber-level or higher.
    Affected if There is at least one user with Subscriber-level access or higher, making the LFI attack surface accessible.
  4. Check for Multisite configuration
    Inspect the wp-config.php file in the WordPress root directory for the line define( 'MULTISITE', true ); or check the Network Admin section if visible in the dashboard.
    Affected if WordPress is configured as a Multisite installation, which would allow the additional privilege escalation impact (Super Administrator password modification).

A user is affected if the WPGYM plugin is installed with version 67.7.0 or lower and there is at least one user with Subscriber-level access or higher in the WordPress environment.

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

Immediately update the WPGYM plugin to the latest version once available. If an update is not available, disable the plugin entirely. Additionally, restrict user permissions to the minimum required and monitor for any suspicious file inclusion activity.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation5.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,460
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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