Stored XSS via unsanitized Markdown blog content
Published Jan 30, 2026 · Updated Jan 30, 2026
Stored XSS in Orchard Core 1.0 allows remote authenticated users to execute scripts in visitors' browsers through crafted blog posts. The MarkdownBodyPart.Source field accepts raw script markup during blog-post creation and publishes it without default sanitization. Content-editor access is required, and viewing the published post executes the stored script in each visitor's Orchard Core session.
Summary
What happened
Stored XSS in Orchard Core 1.0 allows remote authenticated users to execute scripts in visitors' browsers through crafted blog posts. The MarkdownBodyPart.Source field accepts raw script markup during blog-post creation and publishes it without default sanitization. Content-editor access is required, and viewing the published post executes the stored script in each visitor's Orchard Core session.
The record
- CVE
- CVE-2020-37019
- Published
- Jan 30, 2026
- Updated
- Jan 30, 2026
- Vendor
- Orchard Core
- Product
- Orchard Core
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 30, 2026CVE publishedPublication date reported by the CVE source.
- Jan 30, 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=1.0
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
- Orchard Core RC1 persistent XSS reproductionproof 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