Invelity Product Feeds Plugin up to 1.2.6 on WordPress Requests createManageFeedPage cross-site request forgery

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Invelity Product Feeds Plugin up to 1.2.6 on WordPress. This vulnerability affects the function createManageFeedPage of the component Requests Handler. The manipulation leads to cross-site request forgery. This vulnerability is uniquely identified as CVE-2025-14037. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in Invelity Product Feeds Plugin up to 1.2.6 on WordPress and classified as problematic. This issue affects the function createManageFeedPage of the component Requests Handler. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. Using CWE to declare the problem leads to CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. Impacted is integrity. The summary by CVE is:

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.

The weakness was disclosed by Muhammad Yudha. The advisory is shared at wordfence.com. The identification of this vulnerability is CVE-2025-14037 since 12/04/2025. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• WordPress Plugin

Vendor

• Invelity

Name

• Product Feeds Plugin

Version

• 1.2.0
• 1.2.1
• 1.2.2
• 1.2.3
• 1.2.4
• 1.2.5
• 1.2.6

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion