# CVE-2026-25567: WeKan IDOR in card comment creation API

Source: https://junglewise.ai/threats/cve-2026-25567-wekan-idor-in-card-comment-creation-api  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-02-07. Updated: 2026-07-14  
License: CC BY 4.0 with a link back

CVE-2026-25567 · Severity: medium · CVSS 4.3 · Published 2026-02-07

WeKan is an open-source project management tool used to organize tasks on visual boards. A security flaw in the software's comment system allows a logged-in user to post comments that appear to come from a different user. This could be used to spread misinformation, forge approvals, or damage the reputation of other team members within the platform.

Technologies: [WeKan](https://junglewise.ai/threats/technologies/wekan). Vendors: [WeKan](https://junglewise.ai/threats/vendors/wekan).

## Quick answers

**Is CVE-2026-25567 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-25567 being exploited in the wild.

**How severe is CVE-2026-25567?** Medium severity, with a CVSS score of 4.3, published 7 February 2026.

**Which products and versions are affected?** WeKan < 8.19.

**Is there a fix for CVE-2026-25567?** A patch was published on 2026-02-07: Fixed in version 8.19 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-25567 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-25567?** Check whether you run WeKan at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

An Insecure Direct Object Reference (IDOR) exists in the card comment creation API of WeKan versions prior to 8.19. The vulnerability stems from the API endpoint's reliance on an 'authorId' field provided within the request body without verifying it against the authenticated user's actual session identity. An attacker with valid login credentials can submit a request containing the identifier of another user to attribute a comment to them. This issue is categorized as CWE-639 (Authorization Bypass Through User-Controlled Key) and was addressed in version 8.19 by removing the user-controlled authorId parameter from the API route.

## Affected products

- WeKan WeKan < 8.19

## Timeline

- 2026-02-07: disclosed
- 2026-02-07: advisory
- 2026-02-07: patched: Fixed in version 8.19

## References

- [https://github.com/wekan/wekan/commit/67cb47173c1a152d9eaf5469740992b2dacdf62d](https://github.com/wekan/wekan/commit/67cb47173c1a152d9eaf5469740992b2dacdf62d)
- [https://wekan.fi/](https://wekan.fi/)
- [https://www.vulncheck.com/advisories/wekan-card-comment-author-spoofing-via-user-controlled-authorid](https://www.vulncheck.com/advisories/wekan-card-comment-author-spoofing-via-user-controlled-authorid)

## Related threats

- [Wekan ReDoS in user search via unescaped regex](https://junglewise.ai/threats/cve-2026-119300-wekan-is-open-source-kanban-built-with-meteor-prior-to-11-11-the)
- [Wekan authentication bypass via X-Forwarded-For spoofing in header-login](https://junglewise.ai/threats/cve-2026-55652-wekan-authentication-bypass-via-x-forwarded-for-spoofing-in)
- [Wekan broken access control in DDP update rules](https://junglewise.ai/threats/cve-2026-55234-wekan-broken-access-control-in-ddp-update-rules)
- [Wekan missing authorization in cloneBoard method](https://junglewise.ai/threats/cve-2026-53447-wekan-missing-authorization-in-cloneboard-method)
- [Wekan SSRF in webhook integration URLs](https://junglewise.ai/threats/cve-2026-53446-wekan-ssrf-in-webhook-integration-urls)