CVE-2025-60153
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in wpshuffle Subscribe To Unlock subscribe-to-unlock allows PHP Local File Inclusion.This issue affects Subscribe To Unlock: from n/a through <= 1.1.5.
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 confidenceThe wpshuffle Subscribe To Unlock WordPress plugin (version 1.1.5 and below) contains a Local File Inclusion vulnerability where user-supplied input is used in include/require statements without proper sanitization, allowing attackers to include arbitrary PHP files from the server.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedCheck if the wpshuffle-subscribe-to-unlock directory exists in wp-content/plugins/ on the WordPress serverAffected if The plugin directory exists on the server
-
Check the installed plugin versionRead the main plugin file (e.g., wpshuffle-subscribe-to-unlock.php) and look for the 'Version:' header in the plugin comments, or check the version in the WordPress admin plugins pageAffected if The version is 1.1.5 or lower
-
Identify vulnerable file inclusion codeSearch plugin PHP files for include, require, include_once, or require_once statements that use variables from $_GET, $_POST, or $_REQUEST without sanitization (e.g., include($_GET['page']); or require($file);)Affected if Unsanitized user input is used in include/require statements
-
Check for exposed vulnerable endpointsReview WordPress rewrite rules and plugin route handlers to identify any publicly accessible URLs that trigger the vulnerable include/require codeAffected if The vulnerable code can be triggered via HTTP requests with user-controlled file paths
-
Inspect the plugin's AJAX or admin actionsExamine admin-ajax.php or admin-post.php handlers registered by the plugin for file inclusion parameters that accept path traversal characters like ../Affected if The plugin accepts path traversal input in file inclusion functions
If the Subscribe To Unlock plugin version 1.1.5 or lower is installed and contains unsanitized include/require statements that can be triggered via HTTP parameters, the environment is affected by this LFI vulnerability.
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 dataUpgrade to the latest version of the Subscribe To Unlock plugin once available, or disable the plugin as a temporary measure. If immediate patching is not possible, implement web application firewall rules to block suspicious file inclusion requests.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60153 — 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-60153 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