How severe is GHSA-4h72-34j6-j8x7?

GHSA-4h72-34j6-j8x7 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-4h72-34j6-j8x7?

GHSA-4h72-34j6-j8x7 affects the following packages: malojaserver (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-4h72-34j6-j8x7?

Update malojaserver to 3.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4h72-34j6-j8x7 is resolved across your whole dependency graph.

How do I detect GHSA-4h72-34j6-j8x7 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for malojaserver, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-4h72-34j6-j8x7 if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-4h72-34j6-j8x7?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4h72-34j6-j8x7 can be triaged on real exposure rather than presence alone.

Is GHSA-4h72-34j6-j8x7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-4h72-34j6-j8x7 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-4h72-34j6-j8x7 published, and has it been updated?

GHSA-4h72-34j6-j8x7 was published on December 18, 2023 and was last updated on December 6, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

GHSA-4h72-34j6-j8x7 — malojaserver

MEDIUMFix: krateng/maloja@febaff9

GHSA-4h72-34j6-j8x7 is a medium-severity (CVSS 5.4) vulnerability in malojaserver. A fix is available for malojaserver — see the affected versions and patch details below.

Maloja error page XSS vulnerability

Published

Dec 18, 2023

Updated

Dec 6, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 6, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍malojaserver

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`malojaserver`	all versions	3.2.2`pip install --upgrade 'malojaserver==3.2.2'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for malojaserver, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update malojaserver to 3.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4h72-34j6-j8x7 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-4h72-34j6-j8x7 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-4h72-34j6-j8x7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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

O3 Security · Impact-Aware SCA

Is GHSA-4h72-34j6-j8x7 in your dependencies?

O3 Security finds GHSA-4h72-34j6-j8x7 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works