Code execution via unsanitized markdown preview
Published Jan 16, 2026 · Updated Jan 16, 2026
Persistent XSS in vesparny Marky 0.0.1 allows context-dependent attackers to execute code by supplying a crafted markdown file. The live-preview renderer inserts markdown-it output into Electron without sanitizing raw HTML or event-handler attributes. A victim must open the malicious file; the embedded handler then runs through Electron's Node.js process APIs, enabling commands under the victim's account.
Summary
What happened
Persistent XSS in vesparny Marky 0.0.1 allows context-dependent attackers to execute code by supplying a crafted markdown file. The live-preview renderer inserts markdown-it output into Electron without sanitizing raw HTML or event-handler attributes. A victim must open the malicious file; the embedded handler then runs through Electron's Node.js process APIs, enabling commands under the victim's account.
The record
- CVE
- CVE-2021-47839
- Published
- Jan 16, 2026
- Updated
- Jan 16, 2026
- Vendor
- vesparny
- Product
- Marky
- Classifications
- CWE-79, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 16, 2026CVE publishedPublication date reported by the CVE source.
- Jan 16, 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=0.0.1
What conditions does exploitation require?
What is affected?
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
- ExploitDB 49831 Marky persistent XSSfunctional · 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