VulnerabilityPublished 20 Aug 2025

CVE-2025-57730: JetBrains IntelliJ IDEA · Basic XSS

Affects JetBrains IntelliJ IDEASource CVE Database V5

Not known to be exploited · CVSS 5.2 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.2Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
JetBrains IntelliJ IDEA	Affected =0	Fixed in–

AI-suggested

To mitigate CVE-2025-57730, European organizations should: 1) Immediately restrict access to development environments running IntelliJ IDEA, especially the Remote Development feature, ensuring only trusted users have local and remote access. 2) Monitor for updates from JetBrains and apply patches promptly once released. 3) Implement strict privilege management to limit the ability of users to execute or inject code within the IDE environment. 4) Employ network segmentation to isolate development environments from broader corporate networks, reducing the risk of lateral movement. 5) Use endpoint protection solutions capable of detecting anomalous behavior within developer machines. 6) Educate developers about the risks of opening untrusted projects or files within IntelliJ IDEA. 7) Consider temporary disabling or limiting the Remote Development feature if feasible until a patch is available. 8) Conduct code reviews and integrity checks to detect unauthorized changes potentially resulting from exploitation. These steps go beyond generic advice by focusing on access control, environment isolation, and proactive monitoring tailored to the development context.

Description

In JetBrains IntelliJ IDEA before 2025.2 hTML injection was possible via Remote Development feature

Impact

For European organizations, this vulnerability poses a risk primarily to software development teams using IntelliJ IDEA, especially those leveraging the Remote Development feature. The potential impact includes unauthorized access to sensitive source code, intellectual property, and possibly credentials stored or used within the IDE. This can lead to intellectual property theft, code tampering, or insertion of malicious code into software products. Given the collaborative nature of modern software development, an attacker exploiting this vulnerability could compromise the integrity of software builds, leading to downstream supply chain risks. Confidentiality breaches could also expose proprietary algorithms or business logic, affecting competitive advantage. While availability is not impacted, the integrity and confidentiality concerns are significant for organizations with strict compliance requirements such as GDPR. The risk is heightened in environments where developers use shared or remotely accessible development environments without strict access controls. European organizations with large software development operations or those in regulated industries (finance, healthcare, critical infrastructure) should be particularly vigilant.

CWE-80Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) (opens in a new tab)
Variant weaknessLikelihood of exploit: HighOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages.
Implementation
Carefully check each input parameter against a rigorous positive specification (allowlist) defining the specific characters and format allowed. All input should be neutralized, not just parameters that the user is supposed to specify, but all data in the request, including hidden fields, cookies, headers, the URL…
Implementation · Output Encoding
Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8.
Implementation
With Struts, write all data from form beans with the bean's filter attribute set to true.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
V5.3.3 (opens in a new tab)
Attack patterns
XSS Targeting Non-Script Elements (opens in a new tab)
PHP Remote File Inclusion (opens in a new tab)
XSS Through HTTP Query Strings (opens in a new tab)
XSS Through HTTP Headers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

jetbrains.com/privacy-security/issues-fixed/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Aug 2025, 09:35 UTC

WeaknessesCWE-80

Technical details

References

Community reviews

Related threats