Vulnerability Database · npm · payload · Version
payload 3.92.0
3.92.0 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 0 High 0 Medium 1 Low 0 Unrated 0
-
Released 22 Oct 2026
Status latest release
Licence MIT
Also known from other sources 0
Newer releases 300
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
payload 3.92.0 vulnerabilities
1 vulnerability cover payload 3.92.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Payload CMS default account-unlock access allows authenticated users to reset other accounts' lockouts | 5.3 medium | No fix published | 26 Jun 2026 |
Looking for another version, or everything Vulert holds for payload?
Questions
About payload 3.92.0
Is payload 3.92.0 vulnerable?
Yes. 1 vulnerability in the Vulert database cover payload 3.92.0: 0 critical, 0 high, 1 medium and 0 low. Each entry above names the fixed version to move to.
Is 3.92.0 the latest release of payload?
Yes. 3.92.0 is the current release, published 22 Oct 2026. Staying on the current line is what keeps you inside the publisher's fixes.
How do I monitor payload for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the payload version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.