Skip to main content
VulnerabilityPublished

CVE-2026-127215: Kanbanz (WordPress plugin) · Insecure Direct Object Reference

Affects Kanbanz (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.6 High : upgrade to 1.0.3 soon.

Data as of 13 Nov 2026, 20:18 UTC

CVSS 4.0 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.6
CNA (VulnCheck)CVSS 3.18.1
Patch
Available – fixed in 1.0.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade Kanbanz (WordPress plugin) to 1.0.3.

Affected software

ProductAffectedFixed in
SoftaculousKanbanzAffected
  • <1.0.3
Fixed in
  • 1.0.3

AI-suggested

Upgrade Kanbanz plugin to version 1.0.3 or later, where the access control checks have been properly implemented and this vulnerability is fixed. No other mitigations are specified or required once the plugin is updated.

Description

Kanbanz plugin for WordPress versions before 1.0.3 contains an authorization bypass vulnerability allowing authenticated Kanban Staff users to access and modify boards they do not belong to. This is due to missing access control checks in admin-ajax handlers, enabling attackers to manipulate board_id or task_id parameters arbitrarily. Exploitation can lead to unauthorized reading of sensitive task data, modification of status columns, subtasks, labels, comments, attachments, and task creation on other teams' boards. The issue is fixed in version 1.0.3.

References

Community reviews

Loading reviews…