# CVE-2025-14037: Invelity Products Feeds <= 1.2.6 - Cross-Site Request Forgery to Arbitrary File Deletion

> Authenticated administrators can delete arbitrary server files via path traversal if tricked into clicking a malicious link.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Mar 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-f926-gc7c-947h

## What is CVE-2025-14037?

CVE-2025-14037 is a high-severity vulnerability in Invelity Product Feeds, published on 21 Mar 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

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. 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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2025-14037?


## How do I fix CVE-2025-14037?

No fix has been published for CVE-2025-14037 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-14037 being exploited?

There is no known exploitation of CVE-2025-14037 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14037 and fix it if it is affected.

What it is: CVE-2025-14037 is a high-severity vulnerability in Invelity Product Feeds, published on 21 Mar 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-14037 in the wild and no public exploit code.

Affected product: Invelity Product Feeds. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-14037/ (Markdown: https://insights.sbomify.com/CVE-2025-14037/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-14037
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-14037
- OSV: https://osv.dev/vulnerability/CVE-2025-14037

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-14037/
Summaries are generated and may contain mistakes; the official description above is the record.