# CVE-2020-36735: Cross-site request forgery in ERP: Complete HR, Accounting & CRM Suite with WooCommerce CRM Support

> Unauthenticated attackers can modify plugin settings by tricking administrators into clicking a link due to missing nonce validation.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Jul 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-mx34-89f5-9x9v

## What is CVE-2020-36735?

CVE-2020-36735 is a medium-severity vulnerability in wedevs ERP: Complete HR, Accounting & CRM Suite with WooCommerce CRM Support, published on 1 Jul 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

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

## Which versions are affected by CVE-2020-36735?

It affects 1 product.


Products: Wedevs Wp Erp.

## How do I fix CVE-2020-36735?

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

## Is CVE-2020-36735 being exploited?

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

## Other vulnerabilities in wedevs ERP: Complete HR, Accounting & CRM Suite with WooCommerce CRM Support

- [CVE-2024-6666](https://insights.sbomify.com/CVE-2024-6666/): WP ERP <= 1.13.0 - Authenticated (Accounting Manager+) SQL Injection via vendor_id (high 8.8)
- [CVE-2024-21747](https://insights.sbomify.com/CVE-2024-21747/): WordPress WP ERP Plugin <= 1.12.8 is vulnerable to SQL Injection (high 7.6)
- [CVE-2024-12812](https://insights.sbomify.com/CVE-2024-12812/): WP ERP < 1.13.4 - Custom+ Unauthorized Access to Terminated Employee Information (high 7.5)
- [CVE-2024-1173](https://insights.sbomify.com/CVE-2024-1173/): SQL injection in ERP: Complete HR, Accounting & CRM Suite with WooCommerce CRM Support (high 7.2)
- [CVE-2024-0952](https://insights.sbomify.com/CVE-2024-0952/): WP ERP <= 1.12.9 - Authenticated (Accounting Manager+) SQL Injection via id (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36735 and fix it if it is affected.

What it is: CVE-2020-36735 is a medium-severity vulnerability in wedevs ERP: Complete HR, Accounting & CRM Suite with WooCommerce CRM Support, published on 1 Jul 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-36735 in the wild and no public exploit code.

Affected product: wedevs ERP: Complete HR, Accounting & CRM Suite with WooCommerce CRM Support. 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-2020-36735/ (Markdown: https://insights.sbomify.com/CVE-2020-36735/index.md)
```

## Sources

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

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