Security readout for executives and security teams
Plain-English summary
WeKan before 8.19 allowed logged-in users to make card comments appear as if another user wrote them. This is not a system takeover issue, but it can undermine trust in audit trails, project records, and accountability inside teams using WeKan.
Executive priority
Treat as a moderate-priority integrity issue. Patch during the next normal maintenance window, faster for regulated, high-trust, or customer-facing collaboration environments where attribution matters.
Technical view
The card comment creation API accepted a user-controlled authorId in the request body. Because authorization did not bind the recorded author to the authenticated session, an authenticated user could create comments attributed to another user. The issue is classified as CWE-639 IDOR with CVSS 4.0 score 5.3.
Likely exposure
Exposure is limited to organizations running WeKan versions before 8.19, especially deployments with multiple authenticated users. The source bundle does not establish unauthenticated exposure or identify specific hosted services beyond WeKan itself.
Exploitation context
Sources do not report active exploitation, and the CVE is not listed as KEV. Exploitation requires an authenticated user and knowledge of another user's identifier. The practical risk is integrity damage: false attribution, audit confusion, and misuse of trusted comments.
Researcher notes
The affected-version metadata in the bundle is sparse, but the title and description state WeKan before 8.19. No source in the bundle supports public exploit availability or active exploitation. Validation should focus on authorization binding, not payload reproduction.
Mitigation direction
- Upgrade WeKan to 8.19 or later where feasible.
- Review the referenced patch and vendor guidance before rollout.
- Restrict WeKan access to trusted users until patched.
- Review recent comments for suspicious or disputed attribution.
Validation and detection
- Inventory deployed WeKan versions and identify any before 8.19.
- Confirm the deployed build includes commit 67cb47173c1a152d9eaf5469740992b2dacdf62d or equivalent fix.
- In staging, verify comment authorship is derived from the authenticated session.
- Check whether audit or moderation workflows rely on comment author identity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-25567 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
5.3MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/wekan/wekan/commit/67cb47173c1a152d9eaf5469740992b2dacdf62dCVE reference, VulnCheck · patch
- https://wekan.fi/CVE reference, VulnCheck · product
- https://www.vulncheck.com/advisories/wekan-card-comment-author-spoofing-via-user-controlled-authoridCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.