CVE-2026-1640

Taskbuilder <= 5.0.2 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Project/Task Comment Creation

2026-02-17 17:31
Tarcísio Luchesi De Almeida Silva (Poystick)

Strategic Overview

Status
Patched in 5.0.3
Affected Plugin
Taskbuilder – Project Management & Task Management Tool With Kanban Board
Affected Version
<= 5.0.2
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-1640
View all Taskbuilder – Project Management & Task Management Tool With Kanban Board vulnerabilities

At a glance

CVE-2026-1640 is a medium-severity Missing Authorization vulnerability in the Taskbuilder WordPress plugin, affecting versions <= 5.0.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 5.0.3; sites on affected versions should update now. Disclosed February 2026, reported by Tarcísio Luchesi De Almeida Silva (Poystick).

Vulnerability Overview

The Taskbuilder – WordPress Project Management & Task Management plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 5.0.2. This is due to missing authorization checks on the project and task comment submission functions (AJAX actions: wppm_submit_proj_comment and wppm_submit_task_comment). This makes it possible for authenticated attackers, with subscriber-level access and above, to create comments on any project or task (including private projects they cannot view or are not assigned to), and inject arbitrary HTML and CSS via the insufficiently sanitized comment_body parameter.

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 interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Taskbuilder <= 5.0.2 takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Taskbuilder the fix is 5.0.3: builds <= 5.0.2 are affected, anything from 5.0.3 onward is not.

Remediation

Update to version 5.0.3, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Taskbuilder 5.0.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-1640https://www.wordfence.com/threat-intel/vulnerabilities/id/66095908-875f-486d-ae77-6015671872dehttps://nvd.nist.gov/vuln/detail/CVE-2026-1640

Related records

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