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

CVE-2025-54017

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

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 Cozmoslabs Paid Member Subscriptions paid-member-subscriptions allows PHP Local File Inclusion.This issue affects Paid Member Subscriptions: from n/a through <= 2.15.4.

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

This is a PHP Local File Inclusion vulnerability in the Cozmoslabs Paid Member Subscriptions WordPress plugin (versions through <=2.15.4). The improper control of filename for include/require statements allows attackers to include local PHP files, potentially leading to arbitrary code execution or exposure of sensitive server files.

MitigationUpdate to the latest version of Paid Member Subscriptions as soon as a patched release is available. If an update is unavailable, consider temporarily disabling the plugin or implementing web application firewall rules to block suspicious file inclusion requests.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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. Confirm Paid Member Subscriptions plugin is installed
    Access WordPress admin panel, go to Plugins > Installed Plugins, and look for 'Paid Member Subscriptions' by Cozmoslabs in the list
    Affected if Plugin is not found in the installed plugins list
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, click on the Paid Member Subscriptions plugin to view its details, or check the plugin files in /wp-content/plugins/paid-member-subscriptions/ for a version file or header comment in the main PHP file
    Affected if Version is 2.15.4 or lower (any version through 2.15.4)
  3. Verify plugin is active
    In WordPress admin > Plugins > Installed Plugins, confirm the Paid Member Subscriptions plugin shows as 'Active'
    Affected if Plugin is active and vulnerable version is installed
  4. Review access logs for suspicious include requests
    Check web server access logs (typically in /var/log/apache2/ or /var/log/nginx/) for unusual GET/POST requests containing '../' path traversal patterns or direct file references to plugin PHP files
    Affected if Logs show LFI attempt patterns targeting the plugin
  5. Check for unauthorized PHP files in plugin directory
    Inspect /wp-content/plugins/paid-member-subscriptions/ for unexpected or recently created PHP files that do not belong to the original plugin package
    Affected if Unrecognized PHP files exist in the plugin directory

The environment is affected if Paid Member Subscriptions plugin version 2.15.4 or lower is installed and active on the WordPress site.

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 to the latest version of Paid Member Subscriptions as soon as a patched release is available. If an update is unavailable, consider temporarily disabling the plugin or implementing web application firewall rules to block suspicious file inclusion requests.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (version > 2.15.4)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Paid Member Subscriptions' plugin by Cozmoslabs
  4. Check the current installed version (should be <= 2.15.4)
  5. Click 'Update Now' to install the latest available version from the WordPress plugin repository
  6. Verify the update was successful and the plugin is functioning normally after the update

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 / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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