Summary
Maloja error page XSS vulnerability
Impact
The error page for a missing path echoes the path back to the user. If this contains HTML, an attacker could execute a script on the user's machine inside the Maloja context and perform authorized actions like scrobbling or deleting scrobbles.
This does not affect the security of your server. The exploit is purely client-side.
Since there is very little incentive to mess with your scrobble data and it requires very specific targeting (an attacker would have to send a user a link to their own server), the severity rating might be misleading.
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
GHSA-4H72-34J6-J8X7 has a CVSS score of 5.4 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.2.2); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The Vulnerability is patched in 3.2.2
Frequently Asked Questions
- What is GHSA-4H72-34J6-J8X7? GHSA-4H72-34J6-J8X7 is a medium-severity cross-site scripting (XSS) vulnerability in malojaserver (pip), affecting versions < 3.2.2. It is fixed in 3.2.2. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- How severe is GHSA-4H72-34J6-J8X7? GHSA-4H72-34J6-J8X7 has a CVSS score of 5.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of malojaserver are affected by GHSA-4H72-34J6-J8X7? malojaserver (pip) versions < 3.2.2 is affected.
- Is there a fix for GHSA-4H72-34J6-J8X7? Yes. GHSA-4H72-34J6-J8X7 is fixed in 3.2.2. Upgrade to this version or later.
- Is GHSA-4H72-34J6-J8X7 exploitable, and should I be worried? Whether GHSA-4H72-34J6-J8X7 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-4H72-34J6-J8X7 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-4H72-34J6-J8X7? Upgrade
malojaserverto 3.2.2 or later.