GHSA-52qp-gwwh-qrg4 is a medium-severity (CVSS 6.2) CWE-670 vulnerability in @scandipwa/magento-scripts. O3 Security confirms whether GHSA-52qp-gwwh-qrg4 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Missing Handler in @scandipwa/magento-scripts
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@scandipwa/magento-scriptsnpmDescription
Impact
After changing the function from synchronous to asynchronous there wasn't implemented handler in the start, stop, exec and logs commands, effectively making them unusable.
Patches
Version 1.5.3 contains patches for the problems described above.
Workarounds
Upgrade to patched or latest (recommended) version npm i @scandipwa/[email protected] or npm i @scandipwa/magento-scripts@latest.
References
New releases always available here: https://github.com/scandipwa/create-magento-app/releases
For more information
If you have any questions or comments about this advisory:
- Open an issue in create-magento-app
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @scandipwa/magento-scripts | ≥ 1.5.1&&< 1.5.3 | 1.5.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @scandipwa/magento-scripts. 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 @scandipwa/magento-scripts to 1.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-52qp-gwwh-qrg4 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-52qp-gwwh-qrg4 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-52qp-gwwh-qrg4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-52qp-gwwh-qrg4 in your dependencies?
O3 detects GHSA-52qp-gwwh-qrg4 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.