How severe is GHSA-8rxg-9g6f-vq9p?

GHSA-8rxg-9g6f-vq9p has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-8rxg-9g6f-vq9p?

GHSA-8rxg-9g6f-vq9p affects the following packages: another-date-range-picker (npm). Ecosystems affected: npm.

How do I fix GHSA-8rxg-9g6f-vq9p?

No patched version of another-date-range-picker has shipped for GHSA-8rxg-9g6f-vq9p 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-8rxg-9g6f-vq9p in my npm dependencies?

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

How do I mitigate GHSA-8rxg-9g6f-vq9p 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-8rxg-9g6f-vq9p actively exploited in the wild?

No public exploit code has been indexed for GHSA-8rxg-9g6f-vq9p 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-8rxg-9g6f-vq9p published, and has it been updated?

GHSA-8rxg-9g6f-vq9p was published on September 1, 2020 and was last updated on December 7, 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

CRITICAL severity

Malicious Package in another-date-range-pickerGHSA-8rxg-9g6f-vq9p

CRITICAL

GHSA-8rxg-9g6f-vq9p is a critical-severity (CVSS 9.8) vulnerability in another-date-range-picker. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 1, 2020

Updated

Dec 7, 2023

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Dec 7, 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, and reverse-dependency count shows how many other packages break if it stays unpatched.

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

another-date-range-pickernpm

41downloads / week

Description

Version 4.1.48 of another-date-range-picker 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

If version 4.1.48 of this module is found installed you will want to replace it with a version before or after 4.1.48. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`another-date-range-picker`	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 another-date-range-picker, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of another-date-range-picker has shipped for GHSA-8rxg-9g6f-vq9p 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 4.1.48 of `another-date-range-picker` 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 If version 4.1.48 of this module is found installed you will want to replace it with a version before or after 4.1.48. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.

O3 Security · Impact-Aware SCA

Is GHSA-8rxg-9g6f-vq9p in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works