Security readout for executives and security teams
Plain-English summary
WeKan before 8.19 may let logged-in users create public boards even when the site is configured to allow private boards only. This can undermine an organization’s privacy policy for project boards and expose board contents more broadly than intended.
Executive priority
Prioritize remediation for teams using WeKan to manage sensitive internal work, customer projects, security tasks, or regulated data. The risk is policy bypass and unintended exposure, not confirmed remote takeover.
Technical view
The issue is an authorization logic flaw, mapped to CWE-863, in server-side enforcement of the allowPrivateOnly setting during board creation. CVSS v4.0 is 7.1, with network access, low privileges, no user interaction, and high integrity impact. Sources identify the fix in WeKan 8.19-era patch material.
Likely exposure
Exposure is most relevant to WeKan deployments before 8.19 where allowPrivateOnly is enabled and ordinary authenticated users can create boards. The supplied affected metadata is sparse, so version confirmation should rely on vendor and advisory references.
Exploitation context
The source bundle does not cite CISA KEV listing or active exploitation. The practical abuse case is an authenticated user bypassing intended board privacy controls by creating a public board. No source in the bundle supports broader unauthenticated compromise.
Researcher notes
Evidence supports an authenticated authorization bypass in board creation. The bundle names versions prior to 8.19 but provides limited structured affected-version detail. Do not assume exploitation in the wild without additional sources such as KEV or vendor incident statements.
Mitigation direction
- Upgrade WeKan to version 8.19 or later.
- Review the referenced WeKan patch and vendor guidance.
- Temporarily restrict board creation to trusted users if upgrade is delayed.
- Audit existing boards for unintended public visibility.
- Convert or remove public boards created against policy.
Validation and detection
- Inventory all WeKan instances and record their versions.
- Check whether allowPrivateOnly is enabled on each instance.
- Review board visibility settings for public boards.
- Confirm post-upgrade board creation enforces private-only behavior.
- Review admin or application logs for unusual board creation activity.
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-25568 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/7ed76c180ede46ab1dac6b8ad27e9128a272c2c8CVE reference, VulnCheck · patch
- https://wekan.fi/CVE reference, VulnCheck · product
- https://www.vulncheck.com/advisories/wekan-allowprivateonly-setting-enforcement-bypassCVE 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.