WeKan up to 8.18 Card Comment Creation API models/cardComments.js authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in WeKan up to 8.18. Affected by this issue is some unknown functionality of the file models/cardComments.js of the component Card Comment Creation API. This manipulation causes authorization. This vulnerability is tracked as CVE-2026-25567. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability classified as problematic was found in WeKan up to 8.18. Affected by this vulnerability is some unknown processing of the file models/cardComments.js of the component Card Comment Creation API. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. As an impact it is known to affect confidentiality, and integrity. The summary by CVE is:
WeKan versions prior to 8.19 contain an insecure direct object reference (IDOR) in the card comment creation API. The endpoint accepts an authorId from the request body, allowing an authenticated user to spoof the recorded comment author by supplying another user's identifier.
The weakness was disclosed by Joshua Rogers as 67cb47173c1a152d9eaf5469740992b2dacdf62d. The advisory is shared at github.com. This vulnerability is known as CVE-2026-25567 since 02/02/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available.
Upgrading to version 8.19 eliminates this vulnerability. Applying the patch 67cb47173c1a152d9eaf5469740992b2dacdf62d is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-5705). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
Website
- Product: https://github.com/wekan/wekan/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.9VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.4
VulDB Temp Score: 5.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 4.3
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-639 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: WeKan 8.19
Patch: 67cb47173c1a152d9eaf5469740992b2dacdf62d
Timeline
02/02/2026 CVE reserved02/08/2026 Advisory disclosed
02/08/2026 VulDB entry created
07/16/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 67cb47173c1a152d9eaf5469740992b2dacdf62d
Researcher: Joshua Rogers
Status: Confirmed
CVE: CVE-2026-25567 (🔒)
GCVE (CVE): GCVE-0-2026-25567
GCVE (VulDB): GCVE-100-344917
EUVD: 🔒
Entry
Created: 02/08/2026 02:05Updated: 07/16/2026 09:17
Changes: 02/08/2026 02:05 (70), 02/08/2026 07:54 (1), 02/11/2026 09:10 (11), 07/16/2026 09:17 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.