How severe is GHSA-m5pf-5894-jmx7?

No CVSS score has been assigned to GHSA-m5pf-5894-jmx7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m5pf-5894-jmx7?

GHSA-m5pf-5894-jmx7 affects the following packages: sailclothjs (npm). Ecosystems affected: npm.

How do I fix GHSA-m5pf-5894-jmx7?

No patched version of sailclothjs has shipped for GHSA-m5pf-5894-jmx7 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-m5pf-5894-jmx7 in my npm dependencies?

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

How do I mitigate GHSA-m5pf-5894-jmx7 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.

Is GHSA-m5pf-5894-jmx7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-m5pf-5894-jmx7 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-m5pf-5894-jmx7 published, and has it been updated?

GHSA-m5pf-5894-jmx7 was published on September 3, 2020 and was last updated on July 25, 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

Not in CISA KEV

Malicious Package in sailclothjsGHSA-m5pf-5894-jmx7

GHSA-m5pf-5894-jmx7 is a security vulnerability in sailclothjs. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 3, 2020

Updated

Jul 25, 2023

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Jul 25, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

sailclothjsnpm

4downloads / week

Description

Version 1.2.6 of sailclothjs contained malicious code. The code when executed in the browser would enumerate password, cvc, cardnumber fields from forms and send the extracted values to https://js-metrics.com/minjs.php?pl=

Recommendation

Remove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.

Users may consider a downgrade to 1.2.5

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`sailclothjs`	all versions	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 sailclothjs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of sailclothjs has shipped for GHSA-m5pf-5894-jmx7 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
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.

Frequently Asked Questions

Version 1.2.6 of `sailclothjs` contained malicious code. The code when executed in the browser would enumerate password, cvc, cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=` ## Recommendation Remove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised. Users may consider a downgrade to 1.2.5

O3 Security · Impact-Aware SCA

Is GHSA-m5pf-5894-jmx7 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works