Browser script execution via stored class metadata
Published Jun 21, 2021 · Updated Jul 4, 2026
Stored XSS in Typesetter 5.1 allows remote attackers to execute script through className or Description fields in Admin/Classes. The public record identifies the two inputs and route but does not disclose the code path or exact neutralization failure that persists the payload. Exploitation requires a user to render the crafted content, exposing data and actions available to that browser session.
Summary
What happened
Stored XSS in Typesetter 5.1 allows remote attackers to execute script through className or Description fields in Admin/Classes. The public record identifies the two inputs and route but does not disclose the code path or exact neutralization failure that persists the payload. Exploitation requires a user to render the crafted content, exposing data and actions available to that browser session.
The record
- CVE
- CVE-2020-19511
- Published
- Jun 21, 2021
- Updated
- Jul 4, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 21, 2021CVE publishedPublication date reported by the CVE source.
- Jul 4, 2026Record 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