What is GHSA-2P62-C4RM-MR72?

GHSA-2P62-C4RM-MR72 is a critical-severity security vulnerability in another-date-picker (npm), affecting versions = 2.0.43. It is fixed in 2.0.45.

How severe is GHSA-2P62-C4RM-MR72?

GHSA-2P62-C4RM-MR72 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of another-date-picker are affected by GHSA-2P62-C4RM-MR72?

another-date-picker (npm) versions = 2.0.43 is affected.

Is there a fix for GHSA-2P62-C4RM-MR72?

Yes. GHSA-2P62-C4RM-MR72 is fixed in 2.0.45. Upgrade to this version or later.

Is GHSA-2P62-C4RM-MR72 exploitable, and should I be worried?

Whether GHSA-2P62-C4RM-MR72 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-2P62-C4RM-MR72 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-2P62-C4RM-MR72?

Upgrade another-date-picker to 2.0.45 or later.

GHSA-2P62-C4RM-MR72 in another-date-picker

Summary

Malicious Package in another-date-picker

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=

Impact

GHSA-2P62-C4RM-MR72 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.0.45); upgrading removes the vulnerable code path.

Affected versions

another-date-picker (= 2.0.43)

Security releases

another-date-picker → 2.0.45 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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.

Frequently Asked Questions

What is GHSA-2P62-C4RM-MR72? GHSA-2P62-C4RM-MR72 is a critical-severity security vulnerability in another-date-picker (npm), affecting versions = 2.0.43. It is fixed in 2.0.45.
How severe is GHSA-2P62-C4RM-MR72? GHSA-2P62-C4RM-MR72 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of another-date-picker are affected by GHSA-2P62-C4RM-MR72? another-date-picker (npm) versions = 2.0.43 is affected.
Is there a fix for GHSA-2P62-C4RM-MR72? Yes. GHSA-2P62-C4RM-MR72 is fixed in 2.0.45. Upgrade to this version or later.
Is GHSA-2P62-C4RM-MR72 exploitable, and should I be worried? Whether GHSA-2P62-C4RM-MR72 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-2P62-C4RM-MR72 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-2P62-C4RM-MR72? Upgrade another-date-picker to 2.0.45 or later.