CVE-2025-68552
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 WebCodingPlace WooCommerce Coming Soon Product with Countdown woo-coming-soon-product allows PHP Local File Inclusion.This issue affects WooCommerce Coming Soon Product with Countdown: from n/a through <= 5.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 confidenceThis is a Local File Inclusion (LFI) vulnerability in the WooCommerce Coming Soon Product with Countdown WordPress plugin. The plugin fails to properly validate file paths in include/require statements, allowing attackers to potentially include arbitrary local PHP files and execute malicious code.
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.
-
Confirm plugin is installedNavigate to WordPress admin > Plugins, or inspect the /wp-content/plugins/ directory for a folder containing 'woocommerce-coming-soon-product' or similar namingAffected if The plugin WooCommerce Coming Soon Product with Countdown is present in the installation
-
Identify installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate the version number displayed for the WooCommerce Coming Soon Product with Countdown plugin; alternatively, check the plugin's main PHP file for a Version header commentAffected if The displayed version is at or below 5.0, or the version cannot be determined (unknown versions should be treated as potentially vulnerable)
-
Review file inclusion parameters in plugin codeSearch plugin source files (particularly PHP files in the plugin directory) for include, require, include_once, or require_once statements that use variable input without proper validation (e.g., $_GET, $_POST, or unsanitized variables in the path)Affected if File inclusion statements accept user-controlled input without validation, indicating the LFI vulnerability is present and exploitable
The environment is affected if the WooCommerce Coming Soon Product with Countdown plugin is installed with version 5.0 or below and contains unprotected file inclusion logic using variable or user input.
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 the plugin to a version beyond 5.0 that contains the security patch. If no patched version exists, disable the plugin until a fix is available or implement input validation on all file inclusion parameters.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68552 — 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-68552 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