GHSA-q9q2-3ppx-mwqf — graylog2-server
HIGHGHSA-q9q2-3ppx-mwqf is a high-severity (CVSS 7.3) vulnerability in org.graylog2:graylog2-server. A fix is available for org.graylog2:graylog2-server — see the affected versions and patch details below.
Graylog Allows Stored Cross-Site Scripting via Files Plugin and API Browser
Real-World Exposure
org.graylog2:graylog2-serverReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.graylog2:graylog2-server | all versions | 6.2.0org.graylog2:graylog2-server:6.2.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.graylog2:graylog2-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.graylog2:graylog2-server to 6.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q9q2-3ppx-mwqf is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-q9q2-3ppx-mwqf can be triaged on real exposure rather than presence alone.
Tailored to GHSA-q9q2-3ppx-mwqf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-q9q2-3ppx-mwqf in your dependencies?
O3 Security finds GHSA-q9q2-3ppx-mwqf across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.