InfoCode
How to fix: Credential Management API Usage
Credential Management API detected.
Why it matters
Handles sensitive credential storage.
This API stores and retrieves credentials.
How to fix it
- 1Use properly with HTTPS and security best practices.
Code examples
Credential Management: store only after explicit login
if ("credentials" in navigator) {
// Store credentials only after successful authentication
const cred = new PasswordCredential({
id: email,
password: password,
});
await navigator.credentials.store(cred);
}References
Detected automatically by VulnRadar. The check id is credential-management-api, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is Credential Management API Usage?
- VulnRadar rates this info severity in the code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id credential-management-api, which stays the same between runs so you can filter, diff, or gate CI on it.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.