How severe is GHSA-x86x-qhf8-f37w?

GHSA-x86x-qhf8-f37w has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-x86x-qhf8-f37w?

GHSA-x86x-qhf8-f37w affects the following packages: willdurand/js-translation-bundle (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-x86x-qhf8-f37w?

Update willdurand/js-translation-bundle to 2.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x86x-qhf8-f37w is resolved across your whole dependency graph.

How do I detect GHSA-x86x-qhf8-f37w in my Packagist dependencies?

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

How do I mitigate GHSA-x86x-qhf8-f37w 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-x86x-qhf8-f37w?

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

Is GHSA-x86x-qhf8-f37w actively exploited in the wild?

No public exploit code has been indexed for GHSA-x86x-qhf8-f37w 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-x86x-qhf8-f37w published, and has it been updated?

GHSA-x86x-qhf8-f37w was published on June 7, 2024 and was last updated on December 4, 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

CRITICAL severity

GHSA-x86x-qhf8-f37w — willdurand/js-translation…

CRITICALFix: willdurand/BazingaJsTranslationBundle@7accee9

GHSA-x86x-qhf8-f37w is a critical-severity (CVSS 9.8) vulnerability in willdurand/js-translation-bundle. A fix is available for willdurand/js-translation-bundle — see the affected versions and patch details below.

willdurand/js-translation-bundle potential path traversal attack and remote code injection

Published

Jun 7, 2024

Updated

Dec 4, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

🐘willdurand/js-translation-bundle

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

A path traversal and a javascript code injection vulnerabilities were identified in willdurand/js-translation-bundle versions prior to 2.1.1.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`willdurand/js-translation-bundle`	all versions	2.1.1`composer require willdurand/js-translation-bundle:^2.1.1`

Detection & mitigation playbook

Open-source dependency

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

Tailored to GHSA-x86x-qhf8-f37w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A path traversal and a javascript code injection vulnerabilities were identified in willdurand/js-translation-bundle versions prior to 2.1.1.

O3 Security · Impact-Aware SCA

Is GHSA-x86x-qhf8-f37w in your dependencies?

O3 Security finds GHSA-x86x-qhf8-f37w 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