CVE-2026-68900 wekan CVE debrief

Who should care

Defenders responsible for Wekan deployments should assess exposure and verify version 10.23 or later is in use, especially if board data exports are shared or stored externally. This includes operators, platform administrators, vulnerability management teams, and security teams who need to review and mitigate this vulnerability to prevent potential data theft through XSS attacks and disruption of board functionality.

Why it matters

Defenders should prioritize verifying and upgrading to version 10.23 or later, and review board data exports for potential malicious payloads, as an attacker could exploit this vulnerability to read and transmit board data.

• Potential data theft through XSS attacks
• Possible disruption of board functionality
• Need for verification of version 10.23 or later
• Potential for malicious payloads in board data exports

Technical summary

The addBoardHTMLToZip() function in client/lib/exportHTML.js read a card title and body through textContent, which decoded entity-encoded markup, and then interpolated titleText and allText into content.innerHTML in the exported index.html. This allowed a board member to store an entity-encoded event-handler payload in a card title that remained inert on the live board but was reparsed and executed when a recipient clicked the card in the downloaded HTML export, allowing the script to read and transmit all board data contained in that export, including content added after the attacker's membership was removed. Version 10.23 builds the modal with DOM nodes and assigns untrusted values through textContent, fixing

Defensive priority

Defenders should prioritize verifying and upgrading to version 10.23 or later, and review board data exports for potential malicious payloads.

Recommended defensive actions

• Verify and upgrade to version 10.23 or later
• Review board data exports for potential malicious payloads
• Monitor board activity for suspicious behavior
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. Defenders should verify Wekan version 10.23 or later is in use, especially if board data exports are shared or stored externally. The vulnerability allows an attacker to store an entity-encoded event-handler payload in a card title that remains inert on the live board but is reparsed and executed when a recipient clicks the card in the downloaded HTML export. This issue is fixed in version 10.23, which decou

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.