CVE-2025-30755: OpenGrok 1.14.1 has a reflected Cross-Site Scripting (XSS) issue when producing the cross reference page
Affects Oracle OpenGrokSource CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Sep 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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Oracle Corporation OpenGrok | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-30755, European organizations should implement the following specific actions: 1) Immediately review and restrict access to OpenGrok instances, ensuring they are not publicly accessible and are protected behind strong authentication and network segmentation. 2) Educate developers and users about the risks of clicking on untrusted links, especially those referencing internal tools like OpenGrok. 3) Implement web application firewalls (WAFs) with rules designed to detect and block reflected XSS attempts targeting the 'revision' parameter or similar inputs. 4) Apply input validation and output encoding at the application layer if custom modifications or wrappers around OpenGrok exist, sanitizing all user-supplied parameters before rendering. 5) Monitor logs for suspicious requests containing unusual or script-like content in the revision parameter. 6) Stay alert for official patches or updates from Oracle and plan timely deployment once available. 7) Consider deploying Content Security Policy (CSP) headers to restrict script execution contexts in browsers accessing OpenGrok. These targeted measures go beyond generic advice by focusing on access control, user awareness, and layered defenses tailored to the specific vulnerability vector.
Description
OpenGrok 1.14.1 has a reflected Cross-Site Scripting (XSS) issue when producing the cross reference page. This happens through improper handling of the revision parameter. The application reflects unsanitized user input into the HTML output.