How severe is GHSA-fw3x-2pr2-5j64?

No CVSS score has been assigned to GHSA-fw3x-2pr2-5j64 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-fw3x-2pr2-5j64?

GHSA-fw3x-2pr2-5j64 affects the following packages: geshi/geshi (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-fw3x-2pr2-5j64?

Update geshi/geshi to 1.0.8.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fw3x-2pr2-5j64 is resolved across your whole dependency graph.

How do I detect GHSA-fw3x-2pr2-5j64 in my Packagist dependencies?

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

How do I mitigate GHSA-fw3x-2pr2-5j64 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-fw3x-2pr2-5j64?

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

Is GHSA-fw3x-2pr2-5j64 actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-fw3x-2pr2-5j64, including 1 in-the-wild exploitation 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-fw3x-2pr2-5j64?

GHSA-fw3x-2pr2-5j64 has an EPSS (Exploit Prediction Scoring System) score of 3.2%, placing it in the 87th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-fw3x-2pr2-5j64?

GHSA-fw3x-2pr2-5j64 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-fw3x-2pr2-5j64 published, and has it been updated?

GHSA-fw3x-2pr2-5j64 was published on May 17, 2022 and was last updated on April 14, 2025. 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-fw3x-2pr2-5j64 — geshi/geshi

GHSA-fw3x-2pr2-5j64 is a Path Traversal vulnerability in geshi/geshi. 1 public exploit reference exists, so weaponization risk is real. A fix is available for geshi/geshi — see the affected versions and patch details below.

GeSHi vulnerable to Directory Traversal

Also known asCVE-2012-3521

Published

May 17, 2022

Updated

Apr 14, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

3.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs87th percentile — riskier than 87% of all scored CVEsHighest risk

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.

Real-World Exposure

1 pkg affected

🐘geshi/geshi

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

Multiple directory traversal vulnerabilities in the cssgen contrib module in GeSHi before 1.0.8.11 allow remote attackers to read arbitrary files via a .. (dot dot) in the (1) geshi-path or (2) geshi-lang-path parameter.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`geshi/geshi`	all versions	1.0.8.11`composer require geshi/geshi:^1.0.8.11`

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.

Multiple directory traversal vulnerabilities in the cssgen contrib modul…

sourceforge.netNVDJun 2014

Detection & mitigation playbook

Open-source dependency

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

Tailored to GHSA-fw3x-2pr2-5j64. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-fw3x-2pr2-5j64 in your dependencies?

O3 Security finds GHSA-fw3x-2pr2-5j64 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