How severe is GHSA-gqcf-83rq-gpfr?

No CVSS score has been assigned to GHSA-gqcf-83rq-gpfr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gqcf-83rq-gpfr?

GHSA-gqcf-83rq-gpfr affects the following packages: ibexa/post-install (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-gqcf-83rq-gpfr?

Update ibexa/post-install to 1.0.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gqcf-83rq-gpfr is resolved across your whole dependency graph.

How do I detect GHSA-gqcf-83rq-gpfr in my Packagist dependencies?

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

How do I mitigate GHSA-gqcf-83rq-gpfr 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.

Is GHSA-gqcf-83rq-gpfr actively exploited in the wild?

No public exploit code has been indexed for GHSA-gqcf-83rq-gpfr 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-gqcf-83rq-gpfr published, and has it been updated?

GHSA-gqcf-83rq-gpfr was published on September 14, 2021 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Any storage file can be downloaded from p.sh if full…

Real-World Exposure

1 pkg affected

🐘ibexa/post-install

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

The default configuration for platform.sh (.platform.app.yaml) allows access to uploaded files if you know or can guess their location, regardless of whether roles grant content read access to the content containing those files. If you're using Legacy Bridge, the default configuration also allows access to certain legacy files that should not be readable, including the legacy var directory and extension directories.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ibexa/post-install`	all versions	1.0.4.1`composer require ibexa/post-install:^1.0.4.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ibexa/post-install, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ibexa/post-install to 1.0.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gqcf-83rq-gpfr 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.

Frequently Asked Questions

The default configuration for platform.sh (.platform.app.yaml) allows access to uploaded files if you know or can guess their location, regardless of whether roles grant content read access to the content containing those files. If you're using Legacy Bridge, the default configuration also allows access to certain legacy files that should not be readable, including the legacy var directory and extension directories.

O3 Security · Impact-Aware SCA

Is GHSA-gqcf-83rq-gpfr in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works