Graylog Allows Stored Cross-Site Scripting via Files Plugin and API Browser
Impact
Two minor vulnerabilities were identified in the Graylog2 enterprise server, which can be combined to carry out a stored cross-site scripting attack.
An attacker with the permission FILES_CREATE can exploit these vulnerabilities to upload arbitrary Javascript code to the Graylog2 server, which - upon requesting of the file by a user of the API browser - results in the execution of this Javascript code in the context of the Graylog frontend application.
This enables the attacker to carry out authenticated API requests with the permissions of the logged-in user, thereby taking over the user session.
Patches
The generic API has been removed in 6.2.0 rendering the attack vector unreachable and additional escaping has been added.
Analysis provided by Fabian Yamaguchi - Whirly Labs (Pty) Ltd
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Java / Kotlin (Maven) | org.graylog2:graylog2-server | < 6.2.0 | 6.2.0 |
References
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N- Weakness (CWE)
CWE-79- Platform
- Java / Kotlin (Maven)
- Package
org.graylog2:graylog2-server- Disclosed
- 07.05.2025
- Updated
- 11.10.2026 13:20
Sources and licenses
OSV / GitHub Advisory Database - GHSA-q9q2-3ppx-mwqf - CC BY 4.0
Vulnerability history: org.graylog2:graylog2-server
All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 16
- First → latest
- 05.2022 09.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- High 5
- Medium 8
- Low 3
Disclosures per year
- 2022: 3
- 2023: 3
- 2024: 2
- 2025: 4
- 2026: 4
-
Graylog Allows Stored Cross-Site Scripting via Files Plugin and API Browser this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.