CVE-2020-36745

WP Project Manager <= 2.4.0 - Cross-Site Request Forgery Bypass

2020-09-16 00:00
Jerome Bruandet

Strategic Overview

Status
Patched in 2.4.1
Affected Plugin
Project Manager – AI Powered Project Management, Task Management, Kanban Board & Time Tracker
Affected Version
< 2.4.1
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2020-36745
View all Project Manager – AI Powered Project Management, Task Management, Kanban Board & Time Tracker vulnerabilities

At a glance

CVE-2020-36745 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Project Manager WordPress plugin, affecting versions < 2.4.1. 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 2.4.1; sites on affected versions should update now. Disclosed September 2020, reported by Jerome Bruandet.

Vulnerability Overview

The WP Project Manager plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.4.0. This is due to missing or incorrect nonce validation on the do_updates() function. This makes it possible for unauthenticated attackers to trigger updates 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)

Project Manager < 2.4.1 carries this weakness at do_updates(), and reaching it 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 Project Manager the fix is 2.4.1: builds < 2.4.1 are affected, anything from 2.4.1 onward is not.

Remediation

Update to version 2.4.1, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Project Manager: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Project Manager 2.4.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2020-36745https://www.wordfence.com/threat-intel/vulnerabilities/id/456c13f5-4a8b-4eea-a2a0-f37f8508551bhttps://nvd.nist.gov/vuln/detail/CVE-2020-36745

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C