Stored XSS via unencoded WYSIWYG event handlers
Published May 7, 2020 · Updated Aug 4, 2024
Stored XSS in LeptonCMS 4.5.0 allows remote attackers to execute JavaScript in another user's browser through saved WYSIWYG content. The modules/wysiwyg/save.php handler replaces SCRIPT tags but stores other executable markup, including HTML event handlers, without output encoding. A victim must view the saved content; the script then runs in that user's browser context and can act with that session's privileges.
Summary
What happened
Stored XSS in LeptonCMS 4.5.0 allows remote attackers to execute JavaScript in another user's browser through saved WYSIWYG content. The modules/wysiwyg/save.php handler replaces SCRIPT tags but stores other executable markup, including HTML event handlers, without output encoding. A victim must view the saved content; the script then runs in that user's browser context and can act with that session's privileges.
The record
- CVE
- CVE-2020-12707
- Published
- May 7, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 7, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
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
- LeptonCMS 4.5.0 Persistent Cross-Site Scriptingproof of concept · unverified
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