How severe is GHSA-9j39-4686-m3c4?

No CVSS score has been assigned to GHSA-9j39-4686-m3c4 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9j39-4686-m3c4?

GHSA-9j39-4686-m3c4 affects the following packages: ibexa/core (Packagist), ibexa/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-9j39-4686-m3c4?

Update ibexa/core to 4.5.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9j39-4686-m3c4 is resolved across your whole dependency graph.

How do I detect GHSA-9j39-4686-m3c4 in my Packagist dependencies?

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

How do I mitigate GHSA-9j39-4686-m3c4 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-9j39-4686-m3c4?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-9j39-4686-m3c4 can be triaged on real exposure rather than presence alone.

Is GHSA-9j39-4686-m3c4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-9j39-4686-m3c4 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-9j39-4686-m3c4 published, and has it been updated?

GHSA-9j39-4686-m3c4 was published on March 20, 2024 and was last updated on November 29, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-9j39-4686-m3c4 — ibexa/core

Fix: ibexa/core@7e47231

GHSA-9j39-4686-m3c4 is a security vulnerability in ibexa/core. A fix is available for ibexa/core — see the affected versions and patch details below.

Ibexa Kernel's files with blacklisted extensions can be still saved to drafts

Published

Mar 20, 2024

Updated

Nov 29, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 29, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐘ibexa/core🐘ibexa/core

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

File validation can be configured to reject certain files by file type. When this happens, validation fails, and the content can't be published. However, the file can be saved when saving the content draft. This means unwanted files can be present in storage, even if they are not easily accessible due to the content not being published. The fix ensures these unwanted file types are never stored. An attacker would need to have existing access to create content with a file field type to exploit this.

Patches

See "Patched versions". Commit: https://github.com/ibexa/core/commit/7e472317f7c75f45f72f74c38406952d8bea0de1

References

https://developers.ibexa.co/security-advisories/ibexa-sa-2024-002-file-validation-and-workflow-stages

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ibexa/core`	≥ 4.5.0&&< 4.5.6	4.5.6`composer require ibexa/core:^4.5.6`
🐘Packagist	`ibexa/core`	≥ 4.6.0&&< 4.6.2	4.6.2`composer require ibexa/core:^4.6.2`

Detection & mitigation playbook

Open-source dependency

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

Tailored to GHSA-9j39-4686-m3c4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact File validation can be configured to reject certain files by file type. When this happens, validation fails, and the content can't be published. However, the file can be saved when saving the content draft. This means unwanted files can be present in storage, even if they are not easily accessible due to the content not being published. The fix ensures these unwanted file types are never stored. An attacker would need to have existing access to create content with a file field type to exploit this. ### Patches See "Patched versions". Commit: https://github.com/ibexa/core/commit/7e4

O3 Security · Impact-Aware SCA

Is GHSA-9j39-4686-m3c4 in your dependencies?

O3 Security finds GHSA-9j39-4686-m3c4 across Packagist 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