CVE-2025-52708
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 RealMag777 HUSKY woocommerce-products-filter allows PHP Local File Inclusion.This issue affects HUSKY: from n/a through <= 1.3.7.
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 exists in the RealMag777 HUSKY woocommerce-products-filter plugin (versions <= 1.3.7). The vulnerability stems from improper control of filenames in include/require statements, allowing attackers to manipulate file path parameters to read sensitive local files via directory traversal sequences.
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 plugin installationCheck the WordPress plugins directory for the HUSKY woocommerce-products-filter plugin files. In a standard WordPress setup, this would typically be found under wp-content/plugins/husky-woocommerce-products-filter/ or similar path containing 'husky' and 'products-filter'.Affected if The plugin is installed and active in the WordPress environment.
-
Determine installed versionLocate the main plugin PHP file (often named index.php, main.php, or the plugin's primary file) and search for a version constant or comment header containing version information. Compare the found version to 1.3.7 using standard version comparison.Affected if The installed version is 1.3.7 or lower.
-
Identify file inclusion code patternsSearch the plugin directory for PHP files containing include, include_once, require, or require_once statements where the included path appears to be constructed from request parameters (such as $_GET, $_POST, or similar superglobals).Affected if The plugin code contains include/require statements using unsanitized input from HTTP request parameters.
-
Check for directory traversal protectionExamine the identified include/require code for path sanitization. Look for absence of basename(), realpath(), or allowlist validation on the file path parameter before it is used in the include/require statement.Affected if File path parameters used in include/require statements lack proper path sanitization and are vulnerable to directory traversal (e.g., ../../../etc/passwd).
The environment is affected if the HUSKY woocommerce-products-filter plugin is installed with version 1.3.7 or lower and contains file inclusion code that processes user-supplied file paths without sanitization.
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 dataImplement strict input validation and path sanitization on all file path parameters used in include/require statements. Use basename() to strip directory components and validate against an allowlist of permitted files/directories.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52708 — 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-52708 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