Stored HTML injection via parsed error messages
Published Jan 4, 2023 · Updated Mar 10, 2025
Stored HTML injection in Discourse Mermaid Theme Component 1.0.0 allows remote authenticated users to inject HTML through crafted posts. The applyMermaid error handler assigns a Mermaid parsing error derived from post content to innerHTML, causing markup in the error string to be parsed instead of displayed as text. An account able to create posts is required, and injected markup appears within the affected post when the client-side Mermaid renderer handles an error.
Summary
What happened
Stored HTML injection in Discourse Mermaid Theme Component 1.0.0 allows remote authenticated users to inject HTML through crafted posts. The applyMermaid error handler assigns a Mermaid parsing error derived from post content to innerHTML, causing markup in the error string to be parsed instead of displayed as text. An account able to create posts is required, and injected markup appears within the affected post when the client-side Mermaid renderer handles an error.
The record
- CVE
- CVE-2022-46180
- Published
- Jan 4, 2023
- Updated
- Mar 10, 2025
- Vendor
- Discourse
- Product
- Discourse Mermaid Theme Component
- Classifications
- CWE-79, CWE-74
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 4, 2023CVE publishedPublication date reported by the CVE source.
- Mar 10, 2025Record 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.0
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
No public exploit references are available in this record.
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