CVE-2025-1661
Path Traversal in The HUSKY – Products Filter Professional for WooCommerce plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1
Executive Summary
CVE-2025-1661 is a critical severity vulnerability affecting appsec. It is classified as Path Traversal. Ensure your systems and dependencies are patched immediately to mitigate exposure risks.
Precogs AI Insight
"The HUSKY Products Filter plugin for WooCommerce allows unauthenticated Local File Inclusion (LFI). Attackers manipulate file path parameters to read sensitive server configuration files (like wp-config.php) or execute local PHP files. Precogs Application Security Module audits unvalidated input mapped to file inclusion handlers."
What is this vulnerability?
CVE-2025-1661 is categorized as a critical Path Traversal flaw with a CVSS base score of 9.8. Based on our vulnerability intelligence, this issue occurs when the application fails to securely handle untrusted data boundaries.
The HUSKY – Products Filter Professional for WooCommerce plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.3.6.5 via the 'template' parameter of the woof_text_search AJAX action. This makes it possible for unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.
This architectural defect enables adversaries to bypass intended security controls, directly manipulating the application's execution state or data layer. Immediate strategic intervention is required.
Risk Assessment
| Metric | Value |
|---|---|
| CVSS Base Score | 9.8 (CRITICAL) |
| Vector String | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Published | March 11, 2025 |
| Last Modified | March 19, 2025 |
| Related CWEs | CWE-22 |
Impact on Systems
✅ Data Exfiltration: Attackers can extract sensitive data from backend databases, configuration files, or internal services.
✅ Authentication Bypass: Exploiting this flaw may allow unauthorized access to protected resources and administrative interfaces.
✅ Lateral Movement: Once initial access is gained, attackers can pivot to internal systems and escalate privileges.
How to Fix and Mitigate CVE-2025-1661
- Apply Vendor Patches: Upgrade affected components to their latest, non-vulnerable versions immediately.
- Implement Input Validation: Ensure all user-supplied data is validated, sanitized, and type-checked before processing.
- Deploy Runtime Protection: Use Precogs continuous monitoring to detect exploitation attempts in real time.
- Audit Dependencies: Review and update all third-party libraries and transitive dependencies.
Defending with Precogs AI
The HUSKY Products Filter plugin for WooCommerce allows unauthenticated Local File Inclusion (LFI). Attackers manipulate file path parameters to read sensitive server configuration files (like wp-config.php) or execute local PHP files. Precogs Application Security Module audits unvalidated input mapped to file inclusion handlers.
Use Precogs to continuously scan your codebase, binaries, APIs, and infrastructure for this vulnerability class and related attack patterns. Our AI-powered detection engine combines static analysis with threat intelligence to identify exploitable weaknesses before attackers do.
Vulnerability Code Signature
Attack Data Flow
| Stage | Detail |
|---|---|
| Source | User-supplied filename or path parameter |
| Vector | Path manipulation using dot-dot-slash (../) sequences |
| Sink | File system read/write operation |
| Impact | Unauthorized access to sensitive files (e.g., /etc/passwd), directory traversal |
Vulnerable Code Pattern
// ❌ VULNERABLE: Unvalidated path resolution
public File getFile(String filename) {
String basePath = "/var/www/uploads/";
// Taint sink: permits directory traversal via "../"
return new File(basePath + filename);
}
Secure Code Pattern
// ✅ SECURE: Canonical path validation
public File getFile(String filename) throws IOException {
File baseDir = new File("/var/www/uploads/").getCanonicalFile();
File requestedFile = new File(baseDir, filename).getCanonicalFile();
// Sanitized boundary check
if (!requestedFile.getPath().startsWith(baseDir.getPath())) {
throw new SecurityException("Path traversal attempt detected");
}
return requestedFile;
}
How Precogs Detects This
Precogs AI Analysis Engine utilizes semantic taint tracking to detect insecure path resolution sinks, ensuring file access is strictly bounded.\n