WP ERP | Complete HR solution with recruitment & job listings | WooCommerce CRM & Accounting <= 1.6.3 - Cross-Site Request Forgery Bypass
Strategic Overview
- Status
- Patched in 1.6.4
- Affected Version
< 1.6.4- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2020-36735
At a glance
CVE-2020-36735 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the ERP WordPress plugin, affecting versions < 1.6.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.6.4; sites on affected versions should update now. Disclosed September 2020, reported by Jerome Bruandet.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in ERP < 1.6.4 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For ERP the fix is 1.6.4: builds < 1.6.4 are affected, anything from 1.6.4 onward is not.
Remediation
Update to version 1.6.4, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to ERP: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: ERP 1.6.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in ERP: Complete HR, Accounting & CRM Suite Built for WooCommerce
- 9.8CVE-2026-18080: ERP Arbitrary File Upload
CVE-2026-18080 - 8.8CVE-2024-6666: WP ERP <= 1.13.0 SQL Injection
CVE-2024-6666 - 7.2CVE-2024-1173: WP ERP SQL Injection
CVE-2024-1173 - 7.2CVE-2024-0913: WP ERP <= 1.13.0 SQL Injection
CVE-2024-0913 - 7.2CVE-2024-0609: WP ERP Stored XSS
CVE-2024-0609 - 7.2CVE-2024-0952: WP ERP <= 1.12.9 SQL Injection
CVE-2024-0952 - 7.2CVE-2024-21747: WP ERP <= 1.12.8 SQL Injection
CVE-2024-21747 - 7.2CVE-2023-2744: WP ERP <= 1.12.3 SQL Injection
CVE-2023-2744
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C