Vulnerability Database · npm · wincred · Version

wincred 1.0.1

1.0.1 is affected by 1 vulnerability.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to.

Critical 1 High 0 Medium 0 Low 0 Unrated 0

Released 13 Aug 2019 Licence MIT Also known from other sources 1 Newer releases 2 Database updated 23/Oct/2026

Release and licence data published by the npm registry. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Vulnerabilities affecting this version

wincred 1.0.1 vulnerabilities

1 vulnerability cover wincred 1.0.1. Open the full list in the database.

Vulnerability Severity Fixed version Disclosed
CVE-2021-23399: Arbitrary Command Injection in wincred 9.8 critical No fix published 29 Jun 2021

Looking for another version, or everything Vulert holds for wincred?

All versions → Full vulnerability list →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About wincred 1.0.1

Is wincred 1.0.1 vulnerable?

Yes. 1 vulnerability in the Vulert database cover wincred 1.0.1: 1 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.

Is 1.0.1 the latest release of wincred?

No. 1.0.1 was published 13 Aug 2019, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

How do I monitor wincred for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the wincred version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.