How severe is GHSA-r32x-jhw5-g48p?

No CVSS score has been assigned to GHSA-r32x-jhw5-g48p yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-r32x-jhw5-g48p?

GHSA-r32x-jhw5-g48p affects the following packages: eco (npm). Ecosystems affected: npm.

How do I fix GHSA-r32x-jhw5-g48p?

No patched version of eco has shipped for GHSA-r32x-jhw5-g48p yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-r32x-jhw5-g48p in my npm dependencies?

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

How do I mitigate GHSA-r32x-jhw5-g48p if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-r32x-jhw5-g48p actively exploited in the wild?

No public exploit code has been indexed for GHSA-r32x-jhw5-g48p 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-r32x-jhw5-g48p published, and has it been updated?

GHSA-r32x-jhw5-g48p was published on September 3, 2020 and was last updated on September 28, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Cross-Site Scripting in ecoGHSA-r32x-jhw5-g48p

Fix: sstephenson/eco#67

GHSA-r32x-jhw5-g48p is a security vulnerability in eco. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 3, 2020

Updated

Sep 28, 2021

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Sep 28, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

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.

104other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

econpm

4Kdownloads / week

Description

All versions of eco are vulnerable to Cross-Site Scripting (XSS). The package's default __escape implementation fails to escape single quotes, which may allow attackers to execute arbitrary JavaScript on the victim's browser.

Recommendation

No fix is currently available. Consider using an alternative package until a fix is made available.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`eco`	≥ 0.0.0	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for eco, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of eco has shipped for GHSA-r32x-jhw5-g48p yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

All versions of `eco` are vulnerable to Cross-Site Scripting (XSS). The package's default `__escape` implementation fails to escape single quotes, which may allow attackers to execute arbitrary JavaScript on the victim's browser. ## Recommendation No fix is currently available. Consider using an alternative package until a fix is made available.

O3 Security · Impact-Aware SCA

Is GHSA-r32x-jhw5-g48p in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works