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

CVE-2025-26890

HIGH · 7.5 CVSS v3.1 Published 2025-03-27
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 RealMag777 HUSKY woocommerce-products-filter allows PHP Local File Inclusion.This issue affects HUSKY: from n/a through <= 1.3.6.4.

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 confidence

This is a PHP Local File Inclusion (LFI) vulnerability in the HUSKY woocommerce-products-filter plugin. The vulnerability stems from improper control of filenames used in PHP include/require statements, allowing attackers to manipulate input to include arbitrary local PHP files. This can lead to sensitive data exposure or remote code execution.

MitigationImplement strict input validation and sanitization on all user-supplied parameters used in include/require statements, whitelisting allowed values and preventing path traversal sequences. Update to a patched version of the plugin once available.

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. Verify the HUSKY woocommerce-products-filter plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'HUSKY - woocommerce-products-filter' or check the wp-content/plugins/ directory for a folder named similar to 'woocommerce-products-filter' or 'husky-plugin'
    Affected if The plugin appears in the list of installed WordPress plugins
  2. Identify the installed plugin version
    In WordPress admin, click on the plugin from the Plugins list and view the version number displayed, or open and read the main plugin PHP file (usually named plugin-name.php or index.php) and look for a 'Version:' comment in the file header
    Affected if The version cannot be determined or is lower than the patched version (contact vendor for patch information)
  3. Locate PHP files that handle include or require statements
    Search the plugin directory for PHP files containing include, include_once, require, or require_once statements that use variables in the path (for example: include($something); or include($_GET['param']);)
    Affected if Such dynamic include/require patterns are found in the plugin code
  4. Check if user-supplied input reaches the include/require statements
    Examine the dynamic include/require locations found in step 3 to determine if request parameters (GET, POST, COOKIE) or other user-controllable data flows into these file inclusion functions without proper sanitization
    Affected if User input directly or indirectly reaches include/require functions without validation or path traversal protection
  5. Verify the vulnerable endpoint is accessible
    Attempt to access the identified vulnerable script directly via HTTP (for example: https://yoursite.com/wp-content/plugins/woocommerce-products-filter/somefile.php?param=../../../wp-config.php) using a safe test value to confirm the parameter is processed
    Affected if The endpoint responds and processes the parameter without blocking path traversal sequences

If the plugin is installed, contains dynamic file inclusion code that accepts user input, and the vulnerable parameter is accessible via web request, the environment is likely affected by this LFI vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and sanitization on all user-supplied parameters used in include/require statements, whitelisting allowed values and preventing path traversal sequences. Update to a patched version of the plugin once available.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

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