Script execution and forced unlock via crafted requests
Published Mar 24, 2020 · Updated Aug 4, 2024
Reflected XSS and CSRF in ZendTo before 5.22-2 Beta allow remote attackers to run browser script or submit user-unlock actions. The published records identify unlock.tpl and the administrative unlock flow but do not disclose the unneutralized field or missing request-validation check. The victim must open a crafted request while authenticated to the administrative interface; exploitation runs script in that browser's ZendTo origin or unlocks a user account.
Summary
What happened
Reflected XSS and CSRF in ZendTo before 5.22-2 Beta allow remote attackers to run browser script or submit user-unlock actions. The published records identify unlock.tpl and the administrative unlock flow but do not disclose the unneutralized field or missing request-validation check. The victim must open a crafted request while authenticated to the administrative interface; exploitation runs script in that browser's ZendTo origin or unlocks a user account.
The record
- CVE
- CVE-2020-8985
- Published
- Mar 24, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352, CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 24, 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
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