Stored script execution via unencoded workflow titles
Published Jan 19, 2022 · Updated Aug 2, 2024
Stored cross-site scripting in Orchard Core before 1.2.2 allows remote authenticated users to execute script through workflow titles. The workflow designer passes an Add Task/Event title into LocalizedHtmlString without encoding, so persisted markup is rendered as HTML when the workflow interface displays the activity. An authenticated user able to create or edit workflows must store the title, and another user must view the affected workflow page for the browser to execute it.
Summary
What happened
Stored cross-site scripting in Orchard Core before 1.2.2 allows remote authenticated users to execute script through workflow titles. The workflow designer passes an Add Task/Event title into LocalizedHtmlString without encoding, so persisted markup is rendered as HTML when the workflow interface displays the activity. An authenticated user able to create or edit workflows must store the title, and another user must view the affected workflow page for the browser to execute it.
The record
- CVE
- CVE-2022-0243
- Published
- Jan 19, 2022
- Updated
- Aug 2, 2024
- Vendor
- Orchard Core
- Product
- Orchard Core
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 19, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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=unspecified <1.2.2
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
- Workflow Add Task/Event title 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