CVE-2025-14037
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 · uneditedThe 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. This is due to missing validation and sanitization in the 'createManageFeedPage' function. This makes it possible for authenticated administrator-level attackers to delete arbitrary files on the server via specially crafted requests that include path traversal sequences, granted they can trick an admin into clicking a malicious link.
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 confidenceThe Invelity Product Feeds WordPress plugin (versions up to 1.2.6) contains a path traversal vulnerability in the createManageFeedPage function that allows authenticated administrator-level attackers to delete arbitrary files on the server by crafting requests with path traversal sequences (e.g., ../../). The attack requires social engineering to trick an admin into clicking a malicious link.
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
- Low
- Privileges
- High
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:N/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 is installedLog into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Invelity Product Feeds' in the list of active plugins.Affected if The plugin appears in the installed plugins list, regardless of activation status, the environment is potentially affected.
-
Identify installed plugin versionIn the Plugins list, find the Invelity Product Feeds entry and read the version number displayed beneath the plugin name. Alternatively, inspect the plugin main file header (typically in /wp-content/plugins/invelity-product-feeds/ or similar path) for the 'Version' tag.Affected if The installed version is 1.2.6 or any lower version number, the environment is within the affected range.
-
Confirm admin access level existsCheck if any WordPress user account with Administrator role exists on the site. Navigate to Users > All Users in the admin dashboard to enumerate accounts.Affected if At least one Administrator-level user account exists, the condition for exploitation is present (attacker needs admin privileges).
-
Review access logs for exploitation attemptsExamine web server access logs (Apache error.log, Nginx access.log, or WordPress debug.log) for requests containing path traversal patterns such as '../', '..\', or encoded variations targeting the plugin endpoint, particularly around the createManageFeedPage function or feed management routes.Affected if Log entries show suspicious requests with '../' sequences or unusual file deletion attempts targeting the plugin, exploitation may have occurred.
Your environment is affected if the Invelity Product Feeds plugin is installed at version 1.2.6 or below and any Administrator-level user account exists on the WordPress site.
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 dataUpdate to the latest version of the plugin when available. If no patch is forthcoming, consider removing the plugin. Audit server logs for signs of exploitation and restore any deleted critical files.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14037 — 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-14037 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