Cross-site scripting via unsanitized peer names
Published Mar 22, 2023 · Updated Feb 26, 2025
Cross-site scripting in MiroTalk P2P before commit f535b35 allows remote attackers to execute scripts in another participant's browser. The client accepts a peer's changed Name value over the WebRTC data channel and processes it without input validation or output sanitization. A victim must join the same meeting and render the malicious participant name; execution occurs in the victim's browser context.
Summary
What happened
Cross-site scripting in MiroTalk P2P before commit f535b35 allows remote attackers to execute scripts in another participant's browser. The client accepts a peer's changed Name value over the WebRTC data channel and processes it without input validation or output sanitization. A victim must join the same meeting and render the malicious participant name; execution occurs in the victim's browser context.
The record
- CVE
- CVE-2023-27054
- Published
- Mar 22, 2023
- Updated
- Feb 26, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 22, 2023CVE publishedPublication date reported by the CVE source.
- Feb 26, 2025Record 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
- GitHub issue 139 XSS proof of conceptproof of concept · demonstrated
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