Stored script execution via unsanitized Textile pre elements
Published Dec 12, 2022 · Updated Apr 23, 2025
Stored XSS in Redmine before 4.2.9 and 5.0.x before 5.0.4 allows remote attackers to execute scripts through Textile content. Redcloth3's preformatted-text handling fails to sanitize crafted pre elements before storing and rendering Textile-formatted fields. A victim must view the stored content, and some configurations require the attacker to log in as a registered user.
Summary
What happened
Stored XSS in Redmine before 4.2.9 and 5.0.x before 5.0.4 allows remote attackers to execute scripts through Textile content. Redcloth3's preformatted-text handling fails to sanitize crafted pre elements before storing and rendering Textile-formatted fields. A victim must view the stored content, and some configurations require the attacker to log in as a registered user.
The record
- CVE
- CVE-2022-44637
- Published
- Dec 12, 2022
- Updated
- Apr 23, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 12, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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