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

CVE-2025-60150

HIGH · 7.5 CVSS v3.1 Published 2025-09-26
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 wpshuffle Subscribe to Download subscribe-to-download allows PHP Local File Inclusion.This issue affects Subscribe to Download: from n/a through <= 2.0.9.

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 wpshuffle Subscribe to Download WordPress plugin (versions up to 2.0.9) contains a PHP Local File Inclusion (LFI) vulnerability in the subscribe-to-download functionality. The plugin fails to properly validate or sanitize user-supplied input used in include/require statements, allowing attackers to include arbitrary PHP files from the server.

MitigationUpdate the Subscribe to Download plugin to the latest version once available. As an interim measure, disable the plugin if not essential, ensure PHP's allow_url_include is disabled in php.ini, and implement Web Application Firewall rules to block suspicious include/require 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. Locate the plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'wpshuffle' or 'subscribe-to-download'. If using WP-CLI, run: wp plugin list --search='wpshuffle' or wp plugin list --search='subscribe-to-download'
    Affected if The plugin folder exists in the plugins directory
  2. Identify the installed version
    If the plugin is present, check its main PHP file (usually wpshuffle.php or subscribe-to-download.php) for a 'Version:' header in the plugin comment block. Alternatively, run: wp plugin get wpshuffle --format=json (or the appropriate slug)
    Affected if The reported version is 2.0.9 or lower
  3. Verify subscribe-to-download functionality is active
    Check if the plugin is activated in WordPress: wp plugin status wpshuffle (or the plugin slug) should show 'Active'. Also check WordPress admin under Plugins > Installed Plugins to confirm the plugin is enabled
    Affected if The plugin shows as Active and is not disabled
  4. Test for LFI vulnerability in subscribe-to-download
    If the plugin is active, examine HTTP requests to the subscribe-to-download endpoint. Look for PHP include/require usage in the plugin code (search for 'include' or 'require' with user-supplied variables like $_GET, $_POST, or $_REQUEST). Attempt a safe test by providing a benign file path as a parameter (e.g., ?file=../../../wp-config.php) and check if the server returns file contents
    Affected if The plugin accepts unsanitized input in include/require statements and returns file contents when given arbitrary local paths

If the wpshuffle Subscribe to Download plugin is installed, activated, and running version 2.0.9 or lower, the environment is affected by this LFI vulnerability via the subscribe-to-download functionality.

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 Subscribe to Download plugin to the latest version once available. As an interim measure, disable the plugin if not essential, ensure PHP's allow_url_include is disabled in php.ini, and implement Web Application Firewall rules to block suspicious include/require patterns.

Recommended fix Moderate confidence

Latest available version of Subscribe to Download by wpshuffle (version > 2.0.9)

  1. 1. Check the currently installed version of the Subscribe to Download plugin (by wpshuffle) in WordPress admin under Plugins.
  2. 2. If the installed version is 2.0.9 or lower, the site is vulnerable to PHP Local File Inclusion (CWE-98).
  3. 3. Navigate to Plugins > Add New in WordPress admin.
  4. 4. Search for 'Subscribe to Download' by wpshuffle.
  5. 5. If an updated version is available, update the plugin to the latest version.
  6. 6. If no update is available from the WordPress repository, contact the plugin developer for a patched version or consider removing the plugin if unnecessary.
  7. 7. Verify the update was successful and the plugin is functioning normally.

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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