How severe is GHSA-7fj2-rrq6-rphq?

GHSA-7fj2-rrq6-rphq has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-7fj2-rrq6-rphq?

GHSA-7fj2-rrq6-rphq affects the following packages: melisplatform/melis-asset-manager (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-7fj2-rrq6-rphq?

Update melisplatform/melis-asset-manager to 5.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7fj2-rrq6-rphq is resolved across your whole dependency graph.

How do I detect GHSA-7fj2-rrq6-rphq in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for melisplatform/melis-asset-manager. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-7fj2-rrq6-rphq 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-7fj2-rrq6-rphq?

O3 pinpoints whether GHSA-7fj2-rrq6-rphq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-7fj2-rrq6-rphq actively exploited in the wild?

No public exploit code has been indexed for GHSA-7fj2-rrq6-rphq 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.

What type of vulnerability is GHSA-7fj2-rrq6-rphq?

GHSA-7fj2-rrq6-rphq is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-7fj2-rrq6-rphq published, and has it been updated?

GHSA-7fj2-rrq6-rphq was published on October 11, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-7fj2-rrq6-rphq

HIGH

GHSA-7fj2-rrq6-rphq is a high-severity (CVSS 7.5) Path Traversal vulnerability in melisplatform/melis-asset-manager. O3 Security confirms whether GHSA-7fj2-rrq6-rphq is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

melisplatform/melis-asset-manager vulnerable to Path Traversal

Also known asCVE-2022-39296

Published

Oct 11, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐘melisplatform/melis-asset-manager

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

Description

Impact

Attackers can read arbitrary files on affected versions of melisplatform/melis-asset-manager, leading to the disclosure of sensitive information. Conducting this attack does not require authentication.

Users should immediately upgrade to melisplatform/melis-asset-manager >= 5.0.1.

Patches

This issue was addressed by restricting access to files to intended directories only.

References

https://github.com/melisplatform/melis-asset-manager/commit/a0f75918c049aff78953a0bc91c585153595d1bd

For more information

If you have any questions or comments about this advisory, you can contact:

The original reporters, by sending an email to vulnerability.research [at] sonarsource.com;
The maintainers, by opening an issue on this repository.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`melisplatform/melis-asset-manager`	all versions	5.0.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for melisplatform/melis-asset-manager. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update melisplatform/melis-asset-manager to 5.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7fj2-rrq6-rphq 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 pinpoints whether GHSA-7fj2-rrq6-rphq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-7fj2-rrq6-rphq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Attackers can read arbitrary files on affected versions of `melisplatform/melis-asset-manager`, leading to the disclosure of sensitive information. Conducting this attack does not require authentication. Users should immediately upgrade to `melisplatform/melis-asset-manager` >= 5.0.1. ### Patches This issue was addressed by restricting access to files to intended directories only. ### References - https://github.com/melisplatform/melis-asset-manager/commit/a0f75918c049aff78953a0bc91c585153595d1bd ### For more information If you have any questions or comments about this advis

O3 Security · Impact-Aware SCA

Is GHSA-7fj2-rrq6-rphq in your dependencies?

O3 detects GHSA-7fj2-rrq6-rphq across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works