# CVE-2026-127215: Kanbanz WordPress Plugin < 1.0.3 Broken Access Control via admin-ajax Handlers


- **Severity:** High 8.6 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-r985-2wqx-6gh6

## What is CVE-2026-127215?

CVE-2026-127215 is a high-severity vulnerability in Softaculous Kanbanz, published on 13 Nov 2026. 

### Official description

Kanbanz by Softaculous plugin for WordPress before 1.0.3 contains a broken access control vulnerability that allows authenticated Kanban Staff users to access and modify boards they are not members of by exploiting admin-ajax handlers that fail to call kanbanz_user_can_access_board() or per-task edit checks on attacker-supplied board_id or task_id parameters. Attackers can supply arbitrary board IDs to read sensitive task data, overwrite status columns, subtasks, and labels, inject comments, upload or delete attachments, and create tasks or set WIP limits on boards owned by other teams.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-127215?


## How do I fix CVE-2026-127215?

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

## Is CVE-2026-127215 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-127215 and fix it if it is affected.

What it is: CVE-2026-127215 is a high-severity vulnerability in Softaculous Kanbanz, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-127215 in the wild and no public exploit code.

Affected product: Softaculous Kanbanz. 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-2026-127215/ (Markdown: https://insights.sbomify.com/CVE-2026-127215/index.md)
```

## Sources

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

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