WP ERP Plugin up to 1.6.3 on WordPress Setting cross-site request forgery

Summaryinfo

A vulnerability identified as problematic has been detected in WP ERP Plugin up to 1.6.3 on WordPress. This vulnerability affects the function handle_leave_calendar_filter/add_enable_disable_option_save/leave_policies/process_bulk_action/process_crm_contact of the component Setting Handler. The manipulation leads to cross-site request forgery. This vulnerability is traded as CVE-2020-36735. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in WP ERP Plugin up to 1.6.3 on WordPress (WordPress Plugin). It has been rated as problematic. This issue affects the function handle_leave_calendar_filter/add_enable_disable_option_save/leave_policies/process_bulk_action/process_crm_contact of the component Setting 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 WP ERP | Complete HR solution with recruitment & job listings | WooCommerce CRM & Accounting plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.6.3. This is due to missing or incorrect nonce validation on the handle_leave_calendar_filter, add_enable_disable_option_save, leave_policies, process_bulk_action, and process_crm_contact functions. This makes it possible for unauthenticated attackers to modify the plugins settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

The weakness was shared 07/01/2023. The advisory is shared at wordfence.com. The identification of this vulnerability is CVE-2020-36735 since 06/30/2023. 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

Name

• WP ERP Plugin

Version

• 1.6.0
• 1.6.1
• 1.6.2
• 1.6.3

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