# CVE-2026-1892: WeKan REST API boards.js setBoardOrgs improper authorization

> Remote attackers can bypass authorization checks in the WeKan REST API to modify board organizations, requiring high complexity and difficult exploitability.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-qhqq-r75h-hrvf

## What is CVE-2026-1892?

CVE-2026-1892 is a low-severity missing authorization vulnerability in WeKan, published on 4 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in WeKan up to 8.20. This affects the function setBoardOrgs of the file models/boards.js of the component REST API. Such manipulation of the argument item.cardId/item.checklistId/card.boardId leads to improper authorization. The attack may be launched remotely. A high complexity level is associated with this attack. The exploitability is reported as difficult. Upgrading to version 8.21 mitigates this issue. The name of the patch is cabfeed9a68e21c469bf206d8655941444b9912c. It is suggested to upgrade the affected component.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

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

It affects 1 product.


Products: Wekan Project Wekan.

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

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

## Is CVE-2026-1892 being exploited?

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

## Other vulnerabilities in WeKan

- [CVE-2026-30843](https://insights.sbomify.com/CVE-2026-30843/): Wekan has Cross-Board IDOR in Custom Fields Update Endpoints (critical 9.3)
- [CVE-2026-30844](https://insights.sbomify.com/CVE-2026-30844/): Wekan Vulnerable to SSRF through Lack of Validation or Filtering in Attachment URL Loading (critical 9.3)
- [CVE-2026-30847](https://insights.sbomify.com/CVE-2026-30847/): Wekan Credential Leak via notificationUsers Publication Exposes Password Hashes and Session Tokens (critical 9.3)
- [CVE-2025-65780](https://insights.sbomify.com/CVE-2025-65780/): Missing authorization in n/a (high 8.8)
- [CVE-2026-30846](https://insights.sbomify.com/CVE-2026-30846/): Wekan Exposes All Global Webhook Integrations through globalwebhooks Publication (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1892 is a low-severity missing authorization vulnerability in WeKan, published on 4 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-1892 in the wild and no public exploit code.

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

## Sources

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

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