Security readout for executives and security teams
Plain-English summary
WeKan before 8.19 can let a user who should only read a board change cards through certain API paths. The business risk is unauthorized alteration of work items, approvals, or operational records, not server takeover based on the provided sources.
Executive priority
Treat this as high priority for WeKan environments that rely on board permissions for workflow integrity. It can let trusted read-only users alter records, which may affect approvals, task status, compliance evidence, or incident tracking.
Technical view
This is an authorization flaw in WeKan card update handling. Some card update API paths validate board read access instead of write permission, allowing low-privileged authenticated users with read-only board roles to update card data. It is mapped to CWE-863 and scored CVSS 4.0 7.1 high.
Likely exposure
Exposure is limited to WeKan deployments running versions before 8.19 where users have read-only board roles. Systems without WeKan, without shared read-only board access, or already updated to 8.19 are not indicated as exposed by the source bundle.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. Exploitation requires an authenticated low-privileged user with board read access, no user interaction, and network reachability to the affected application/API.
Researcher notes
Evidence supports an access-control failure, not remote code execution or unauthenticated compromise. The bundle does not enumerate every affected API route or provide exploitation-in-the-wild evidence. Validation should focus on deployed version, role model, authorization checks, and anomalous card modifications.
Mitigation direction
- Upgrade WeKan to version 8.19 or later.
- Apply the referenced upstream patch if maintaining a forked deployment.
- Review read-only board role assignments for unnecessary access.
- Monitor vendor guidance for any additional fixed releases or hardening advice.
Validation and detection
- Inventory all WeKan deployments and record their running versions.
- Confirm no production instance is below WeKan 8.19.
- Review audit logs for card changes made by read-only users.
- Verify deployed authorization logic requires write permission for card updates.
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-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-25565 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
- High
- CVSS
- 7.1 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/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:N/VI:H/VA:N/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
7.1HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/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/181f837d8cbae96bdf9dcbd31beaa3653c2c0285CVE reference, VulnCheck · patch
- https://wekan.fi/CVE reference, VulnCheck · product
- https://www.vulncheck.com/advisories/wekan-read-only-board-roles-can-update-cardsCVE 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.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.