Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.4amended

Maloja error page XSS vulnerability

GHSA-4h72-34j6-j8x7

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (malojaserver 3.2.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.4 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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. Patches The Vulnerability is patched in 3.2.2

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-4h72-34j6-j8x7

  2. Revision 1 · created ·

    Published from osv record GHSA-4h72-34j6-j8x7

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-4h72-34j6-j8x7

Advisory: Maloja error page XSS vulnerability
IDs: GHSA-4h72-34j6-j8x7
Record: https://patchnext.com/advisories/ghsa-4h72-34j6-j8x7 (revision 2, source checked 26 Oct 2026, 13:12 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: malojaserver 3.2.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI malojaserver: affected < 3.2.2; fixed in 3.2.2

## Suggested inspection (read-only)
- `python -m pip show malojaserver`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on malojaserver.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-4h72-34j6-j8x7 (OSV record GHSA-4h72-34j6-j8x7 lists affected ranges: PyPI malojaserver >=0 <3.2.2 (fixed))
- Verified: https://github.com/advisories/GHSA-4h72-34j6-j8x7 (GitHub-reviewed advisory GHSA-4h72-34j6-j8x7 lists affected ranges: PyPI malojaserver >=0 <3.2.2)

Commands are suggestions: review each one before running it.

Loading voting…