How severe is GHSA-2p62-c4rm-mr72?

GHSA-2p62-c4rm-mr72 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-2p62-c4rm-mr72?

GHSA-2p62-c4rm-mr72 affects the following packages: another-date-picker (npm). Ecosystems affected: npm.

How do I fix GHSA-2p62-c4rm-mr72?

Update another-date-picker to 2.0.45 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2p62-c4rm-mr72 is resolved across your whole dependency graph.

How do I detect GHSA-2p62-c4rm-mr72 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for another-date-picker. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-2p62-c4rm-mr72 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-2p62-c4rm-mr72?

O3 pinpoints whether GHSA-2p62-c4rm-mr72 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-2p62-c4rm-mr72 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2p62-c4rm-mr72 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-2p62-c4rm-mr72 published, and has it been updated?

GHSA-2p62-c4rm-mr72 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

GHSA-2p62-c4rm-mr72

CRITICAL

GHSA-2p62-c4rm-mr72 is a critical-severity (CVSS 9.8) vulnerability in another-date-picker. O3 Security confirms whether GHSA-2p62-c4rm-mr72 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Malicious Package in another-date-picker

Published

Sep 1, 2020

Updated

Dec 7, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 7, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦another-date-picker

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

Version 2.0.43 of another-date-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 2.0.43 of this module is found installed you will want to replace it with a version before or after 2.0.43. 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 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`another-date-picker`	≥ 2.0.43&&< 2.0.45	2.0.45

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-picker. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update another-date-picker to 2.0.45 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2p62-c4rm-mr72 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 pinpoints whether GHSA-2p62-c4rm-mr72 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-2p62-c4rm-mr72. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Version 2.0.43 of `another-date-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 2.0.43 of this module is found installed you will want to replace it with a version before or after 2.0.43. 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-2p62-c4rm-mr72 in your dependencies?

O3 detects GHSA-2p62-c4rm-mr72 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 dependencies How O3 SCA works