HTML injection through Remote Development
Published Aug 20, 2025 · Updated Aug 20, 2025
HTML injection in JetBrains IntelliJ IDEA before 2025.2 allows local users to alter rendered content through Remote Development. JetBrains identifies the affected feature but has not published the code locus or the operation that fails to neutralize untrusted HTML. Low-privileged local access is required; published assessments bound the consequence to limited confidentiality and integrity impact without service interruption.
Summary
What happened
HTML injection in JetBrains IntelliJ IDEA before 2025.2 allows local users to alter rendered content through Remote Development. JetBrains identifies the affected feature but has not published the code locus or the operation that fails to neutralize untrusted HTML. Low-privileged local access is required; published assessments bound the consequence to limited confidentiality and integrity impact without service interruption.
The record
- CVE
- CVE-2025-57730
- Published
- Aug 20, 2025
- Updated
- Aug 20, 2025
- Vendor
- JetBrains
- Product
- IntelliJ IDEA
- Classifications
- CWE-80
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 20, 2025CVE publishedPublication date reported by the CVE source.
- Aug 20, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2025.2
What conditions does exploitation require?
What is affected?
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