How severe is GHSA-q88g-qx42-xfrh?

No CVSS score has been assigned to GHSA-q88g-qx42-xfrh yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q88g-qx42-xfrh?

GHSA-q88g-qx42-xfrh affects the following packages: bolt/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-q88g-qx42-xfrh?

Update bolt/core to 4.1.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q88g-qx42-xfrh is resolved across your whole dependency graph.

How do I detect GHSA-q88g-qx42-xfrh in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bolt/core. 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-q88g-qx42-xfrh 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-q88g-qx42-xfrh?

O3 pinpoints whether GHSA-q88g-qx42-xfrh 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-q88g-qx42-xfrh actively exploited in the wild?

No public exploit code has been indexed for GHSA-q88g-qx42-xfrh 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-q88g-qx42-xfrh?

GHSA-q88g-qx42-xfrh 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-q88g-qx42-xfrh published, and has it been updated?

GHSA-q88g-qx42-xfrh was published on February 18, 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.

🐘 Packagist

Not in CISA KEV

GHSA-q88g-qx42-xfrh

Fix: bolt/core#2371

GHSA-q88g-qx42-xfrh is a Path Traversal vulnerability in bolt/core. O3 Security confirms whether GHSA-q88g-qx42-xfrh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Path traversal in bolt/core

Also known asCVE-2021-27367

Published

Feb 18, 2021

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

🐘bolt/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

Controller/Backend/FileEditController.php and Controller/Backend/FilemanagerController.php in Bolt before 4.1.13 allow Directory Traversal.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`bolt/core`	all versions	4.1.13

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bolt/core. 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 bolt/core to 4.1.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q88g-qx42-xfrh 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-q88g-qx42-xfrh 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-q88g-qx42-xfrh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Controller/Backend/FileEditController.php and Controller/Backend/FilemanagerController.php in Bolt before 4.1.13 allow Directory Traversal.

O3 Security · Impact-Aware SCA

Is GHSA-q88g-qx42-xfrh in your dependencies?

O3 detects GHSA-q88g-qx42-xfrh 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