Skip to content

Graylog Allows Stored Cross-Site Scripting via Files Plugin and API Browser

High severity GitHub Reviewed Published May 7, 2025 in Graylog2/graylog2-server • Updated May 7, 2025

Package

maven org.graylog2:graylog2-server (Maven)

Affected versions

< 6.2.0

Patched versions

6.2.0

Description

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

References

@kroepke kroepke published to Graylog2/graylog2-server May 7, 2025
Published to the GitHub Advisory Database May 7, 2025
Reviewed May 7, 2025
Last updated May 7, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N

EPSS score

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-q9q2-3ppx-mwqf

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.