CVE-2023-41592 — froala-editor
MEDIUMCVE-2023-41592 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in froala-editor. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for froala-editor — see the affected versions and patch details below.
Froala Editor Cross-site Scripting vulnerability
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-41592.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
froala-editornpmDescription
Froala Editor v4.0.1 to v4.1.1 was discovered to contain a cross-site scripting (XSS) vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | froala-editor | ≥ 4.0.1&&< 4.1.4 | 4.1.4npm install froala-editor@4.1.4 |
| 🐘Packagist | froala/wysiwyg-editor | ≥ 4.0.1&&< 4.1.4 | 4.1.4composer require froala/wysiwyg-editor:^4.1.4 |
Affected Products
froala editorfroalaResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for froala-editor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update froala-editor to 4.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-41592 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2023-41592 in your dependencies?
Find it across npm, Packagist, including transitive dependencies.