Stored XSS via export innerHTML reparse
Published Aug 19, 2026 · Updated Aug 19, 2026
Stored XSS in HTML export in WeKan 8.72 through 10.22 allows remote authenticated users to execute script via a card title. In addBoardHTMLToZip() in client/lib/exportHTML.js, the export click handler reads card title and body with textContent, which decodes entity-encoded markup, then concatenates titleText and allText into content.innerHTML in the generated index.html, causing a second HTML parse that revives attacker-supplied handlers. Board-member access is required and a recipient must open the downloaded export and click the malicious card; the script runs in the export document and can exfiltrate all board data included there, including cards added after the attacker's membership was removed.
Summary
What happened
Stored XSS in HTML export in WeKan 8.72 through 10.22 allows remote authenticated users to execute script via a card title. In addBoardHTMLToZip() in client/lib/exportHTML.js, the export click handler reads card title and body with textContent, which decodes entity-encoded markup, then concatenates titleText and allText into content.innerHTML in the generated index.html, causing a second HTML parse that revives attacker-supplied handlers. Board-member access is required and a recipient must open the downloaded export and click the malicious card; the script runs in the export document and can exfiltrate all board data included there, including cards added after the attacker's membership was removed.
The record
- CVE
- CVE-2026-68900
- Published
- Aug 19, 2026
- Updated
- Aug 19, 2026
- Vendor
- WeKan
- Product
- WeKan
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- Aug 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 8.72, < 10.23
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-8r5p-4q9j-f5jx proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo