dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-32549

HIGH · 7.5 CVSS v3.1 Published 2025-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in mojoomla WPGYM allows PHP Local File Inclusion. This issue affects WPGYM: from n/a through 65.0.

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 · moderate confidence

Local File Inclusion vulnerability in WPGYM plugin allows attackers to include arbitrary local PHP files through unsanitized input in include/require statements, potentially leading to code execution.

MitigationUpdate WPGYM to the latest patched version when available. If no patch exists, disable the plugin and implement input validation/allowlisting on file inclusion functions, or deploy a WAF rule to block directory traversal patterns.

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

CVSS:3.1/AV:N/AC:H/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
    Check your WordPress wp-content/plugins directory for a folder named 'wpgym', 'wp-gym-management', or similar gym management plugin names. Alternatively, log into WordPress admin and navigate to Plugins to list all installed plugins.
    Affected if The WPGYM plugin or a gym management plugin from WPGYM is present in the plugins directory or listed in WordPress admin.
  2. Determine the installed WPGYM version
    If the plugin folder is found, open the main plugin PHP file (usually named wpgym.php, index.php, or wp-gym-management.php) and locate the version comment or 'Version:' header in the file header. Alternatively, check the plugin's readme.txt file for the version number.
    Affected if The installed version number is lower than the patched version released for CVE-2025-32549, or the version cannot be determined (indicating it may be an older unpatched release).
  3. Inspect file inclusion code for unsanitized input
    In the plugin directory, search for include, require, include_once, or require_once statements that use variables without sanitization (e.g., include($var), require($_GET['page']). Use grep or a text editor to examine PHP files in the include/ folder or any file handling code.
    Affected if Code contains include/require statements using raw user input (GET, POST, or COOKIE parameters) without proper sanitization or validation, enabling directory traversal.
  4. Verify plugin is active
    In WordPress admin under Plugins > Installed Plugins, confirm whether the WPGYM plugin shows as 'Active'. Alternatively, query the WordPress options table for active plugins.
    Affected if The WPGYM plugin is currently activated on the WordPress site, making the vulnerability exploitable.
  5. Check web server logs for exploitation attempts
    Review web server access logs (Apache error.log, Nginx access.log) or WordPress debug logs for patterns like '../', '..\', or requests to include PHP files from outside the plugin directory, particularly those targeting the vulnerable include/require paths.

Your environment is affected if the WPGYM plugin is installed and active with an unpatched version containing unsanitized file inclusion code that allows local PHP file inclusion via user-controlled input.

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 WPGYM to the latest patched version when available. If no patch exists, disable the plugin and implement input validation/allowlisting on file inclusion functions, or deploy a WAF rule to block directory traversal patterns.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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 locally
dbcve dependency scanner

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