Stored XSS via unsafe discussion-title rendering
Published Nov 19, 2022 · Updated Apr 23, 2025
Stored cross-site scripting in Flarum 1.5.0 through 1.6.1 allows remote authenticated users to execute script via discussion titles. Application.tsx parsed the computed title through an element's innerHTML, while app.blade.php rendered the server-side title with unescaped output. An account able to create or rename a discussion must supply the title, and a victim must open that discussion before the injected markup executes.
Summary
What happened
Stored cross-site scripting in Flarum 1.5.0 through 1.6.1 allows remote authenticated users to execute script via discussion titles. Application.tsx parsed the computed title through an element's innerHTML, while app.blade.php rendered the server-side title with unescaped output. An account able to create or rename a discussion must supply the title, and a victim must open that discussion before the injected markup executes.
The record
- CVE
- CVE-2022-41938
- Published
- Nov 19, 2022
- Updated
- Apr 23, 2025
- Vendor
- Flarum
- Product
- Flarum
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 19, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.5.0, < 1.6.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
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