Security readout for executives and security teams
Plain-English summary
WeKan versions before 8.19 may expose attachment metadata to users who should not see it. The issue affects information about attachments, not documented file contents or system control. Business urgency is moderate because an authenticated user could learn metadata across inaccessible boards or cards.
Executive priority
Prioritize remediation in shared or externally reachable WeKan environments. This is not presented as a critical takeover issue, but metadata leakage can expose sensitive project, customer, or operational context.
Technical view
The attachments publication did not properly scope returned attachment metadata to boards and cards accessible to the requesting user. CVSS 4.0 is 5.3 with network access, low complexity, low privileges, no user interaction, and low confidentiality impact.
Likely exposure
Exposure is most likely in WeKan deployments running versions prior to 8.19 where untrusted or semi-trusted authenticated users have accounts.
Exploitation context
The source bundle does not cite active exploitation, and KEV status is false. Public sources identify a patch commit and third-party advisory, but do not provide evidence of weaponized exploitation.
Researcher notes
Evidence supports an attachment metadata disclosure caused by insufficient publication scoping. The CVE lists CWE-203, while the description centers on authorization scoping. Treat product/version details conservatively and rely on WeKan 8.19 or vendor guidance.
Mitigation direction
- Upgrade WeKan to version 8.19 or later.
- Apply the referenced vendor patch if upgrading is not immediately possible.
- Review vendor guidance for any additional configuration or operational recommendations.
- Limit accounts to trusted users until remediation is complete.
- Audit unusual access to attachment metadata where logging supports it.
Validation and detection
- Inventory WeKan instances and confirm their running versions.
- Verify affected systems are updated to 8.19 or later.
- Use authorized test accounts to confirm board and card scoping works as expected.
- Review access-control tests around attachment publication behavior.
- Track the patch commit against deployed source if using a custom build.
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-203: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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-25562 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:N/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:N/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:N/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/6dfa3beb2b6ab23438d0f4395b84bf0749eb4820CVE reference, VulnCheck · patch
- https://wekan.fi/CVE reference, VulnCheck · product
- https://www.vulncheck.com/advisories/wekan-attachments-publication-information-disclosureCVE 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.
Observable Discrepancy
Observable Discrepancy represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.