Browser script execution via crafted title
Published Jan 11, 2020 · Updated Aug 5, 2024
Cross-site scripting in TopList before 2019-09-03 allows remote attackers to execute script in a visitor's browser via a crafted title. The public report identifies title rendering as the injection surface but does not disclose the responsible code path or encoding failure. Exploitation is unauthenticated but requires a visitor to render the affected title; reported impact is limited to browser-accessible data.
Summary
What happened
Cross-site scripting in TopList before 2019-09-03 allows remote attackers to execute script in a visitor's browser via a crafted title. The public report identifies title rendering as the injection surface but does not disclose the responsible code path or encoding failure. Exploitation is unauthenticated but requires a visitor to render the affected title; reported impact is limited to browser-accessible data.
The record
- CVE
- CVE-2019-20377
- Published
- Jan 11, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 11, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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
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