CVE-2025-14037

The Invelity Product Feeds plugin for WordPress is vulnerable to arbitrary file deletion via path traversal in all versions up to, and including, 1.

Verified by Precogs Threat Research
Last Updated: Mar 21, 2026
Base Score
8.1HIGH

Executive Summary

CVE-2025-14037 is a high severity vulnerability affecting appsec. It is classified as CSRF. Ensure your systems and dependencies are patched immediately to mitigate exposure risks.

Precogs AI Insight

"Precogs AI Analysis Engine identifies web application vulnerabilities through semantic code analysis, detecting injection flaws, broken authentication, and insecure data flows across your entire codebase."

Exploit Probability
Elevated (52%)
Public POC
Undisclosed
Exploit Probability
Elevated (52%)
Public POC
Available
Affected Assets
appsecCWE-352

What is this vulnerability?

CVE-2025-14037 is categorized as a critical Path Traversal flaw. Based on our vulnerability intelligence, this issue occurs when the application fails to securely handle untrusted data boundaries.

The Invelity Product Feeds plugin for WordPress is vulnerable to arbitrary file deletion via path traversal in all versions up to, and including, 1.2.6. Th...

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

MetricValue
CVSS Base Score8.1 (HIGH)
Vector StringCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:N/I:H/A:H
PublishedMarch 21, 2026
Last ModifiedMarch 21, 2026
Related CWEsCWE-352

Impact on Systems

Sensitive File Disclosure: Unauthorized access to critical configuration files (/etc/passwd, .env files, private SSH keys).

Application Source Leak: Attackers can download proprietary source code and hardcoded credentials.

Remote Code Execution: By combining with log poisoning, attackers can write PHP/JSP shells into web-accessible directories.

How to fix this issue?

Implement the following strategic mitigations immediately to eliminate the attack surface.

1. Indirect References Avoid using direct file paths. Utilize indirect references (like database IDs) mapped to backend files.

2. Strict Path Resolution If direct paths are required, resolve the absolute path and rigorously verify the path starts with the expected base directory using native OS path resolving functions.

3. Chroot Jails Confine the application processes to highly restricted directory structures (chroot) with minimum readable boundaries.

Vulnerability Signature

// Vulnerable File Access
import os
def get_image(request):
    filename = request.GET.get('file')
    # VULNERABLE: No validation preventing moving upwards in the directory tree
    filepath = os.path.join('/var/www/images/', filename)
    return open(filepath, 'rb').read()

// EXPLOIT PAYLOAD: ?file=../../../../../../../../etc/passwd

References and Sources

Related Vulnerabilitiesvia CWE-352

CVE-2026-41434.3 MEDIUM

The Neos Connector for Fakturama plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 0.

CWE-352
CVE-2026-33324.3 MEDIUM

The Xhanch - My Advanced Settings plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.

CWE-352
CVE-2026-33314.3 MEDIUM

The Lobot Slider Administrator plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 0.

CWE-352
CVE-2026-27236.1 MEDIUM

The Post Snippits plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.

CWE-352
CVE-2026-15034.3 MEDIUM

The login_register plugin for WordPress is vulnerable to Cross-Site Request Forgery to Stored Cross-Site Scripting in all versions up to, and including, 1.

CWE-352
CVE-2026-13934.3 MEDIUM

The Add Google Social Profiles to Knowledge Graph Box plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.

CWE-352