How severe is GHSA-wf7x-fh6w-34r6?

GHSA-wf7x-fh6w-34r6 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-wf7x-fh6w-34r6?

GHSA-wf7x-fh6w-34r6 affects the following packages: ghost (npm). Ecosystems affected: npm.

How do I fix GHSA-wf7x-fh6w-34r6?

Update ghost to version 5.42.1 or later. Run your dependency manager's update command and verify no transitive dependencies pin the vulnerable version. Use O3 Security's SCA scanner to confirm the fix is applied across your entire dependency tree.

Is GHSA-wf7x-fh6w-34r6 actively exploited in the wild?

Yes. There are 4 known exploit references for GHSA-wf7x-fh6w-34r6, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-wf7x-fh6w-34r6?

GHSA-wf7x-fh6w-34r6 has an EPSS (Exploit Prediction Scoring System) score of 94.1%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is GHSA-wf7x-fh6w-34r6?

GHSA-wf7x-fh6w-34r6 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.

Is there exploit tooling available for GHSA-wf7x-fh6w-34r6?

A Nuclei detection template exists for GHSA-wf7x-fh6w-34r6, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-wf7x-fh6w-34r6 published, and has it been updated?

GHSA-wf7x-fh6w-34r6 was published on May 5, 2023 and was last updated on December 6, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-wf7x-fh6w-34r6

HIGH

Path Traversal in Ghost

Also known asBIT-ghost-2023-32235CVE-2023-32235

Published

May 5, 2023

Updated

Dec 6, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

4 known

EPSS Exploitation Probability

via FIRST.org ↗

94.1%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

📦ghost

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Ghost before 5.42.1 allows remote attackers to read arbitrary files within the active theme's folder via /assets/built%2F..%2F..%2F/ directory traversal. This occurs in frontend/web/middleware/static-theme.js.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`ghost`	all versions	5.42.1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52408webappsmultiple

Ghost CMS 5.42.1 - Path Traversal

by İbrahimsql · Aug 11, 2025

Exploit-DB Source

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-wf7x-fh6w-34r6 in your stack?

O3 detects GHSA-wf7x-fh6w-34r6 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works