CVE-2025-30782
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 WP Shuffle Subscribe to Download Lite subscribe-to-download-lite allows PHP Local File Inclusion.This issue affects Subscribe to Download Lite: from n/a through <= 1.2.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 confidenceA PHP Local File Inclusion (LFI) vulnerability in the WP Shuffle Subscribe to Download Lite plugin (versions up to 1.2.9) allows attackers to include arbitrary local files via improperly controlled filename parameters in include/require statements. This can lead to exposure of sensitive server files such as configuration files, credentials, or the wp-config.php file.
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 for the 'wp-shuffle-subscribe-to-download-lite' or 'subscribe-to-download-lite' directory in /wp-content/plugins/Affected if The plugin directory exists in the WordPress plugins folder
-
Check the installed versionOpen the main plugin file (usually index.php or subscribe-to-download-lite.php) and locate the version header comment (e.g., 'Version: 1.2.9')Affected if The version number is 1.2.9 or lower (the affected range is up to 1.2.9)
-
Confirm the plugin is activeQuery the WordPress database or check wp-admin/plugins.php to see if the plugin status is 'active'Affected if The plugin shows as active in WordPress
-
Inspect for vulnerable include/require patternsSearch the plugin PHP files for 'include' or 'require' statements using variable filenames (e.g., include($filename), require($_GET['file']))Affected if Variable-based file includes that accept user input are present in the plugin code
You are affected if the Subscribe to Download Lite plugin is installed, active, and running version 1.2.9 or lower with unprotected include/require statements using user-controlled filenames.
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 dataUpdate the Subscribe to Download Lite plugin to the latest patched version. If no patch is available, disable and remove the plugin immediately. For remediation, implement strict whitelist-based input validation on all file path parameters and use hardcoded include paths rather than user-controlled variables.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-30782 — 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-30782 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