Security readout for executives and security teams
Plain-English summary
This issue affects Strapi sites using the users-permissions plugin when JWT algorithm settings are left implicit. If an attacker already has the JWT secret, they may create tokens using alternate HMAC algorithms, weakening intended authentication controls. The supplied sources do not show active exploitation.
Executive priority
Treat as a targeted configuration and secret-management risk. It is not described as actively exploited, but internet-facing Strapi systems should be reviewed promptly because compromise impact rises sharply if jwtSecret is exposed.
Technical view
The users-permissions plugin does not restrict JWT algorithms when plugin::users-permissions.jwt.algorithm is unset. Sources describe acceptance of HS384 and HS512 alongside HS256. Exploitation requires possession of jwtSecret, so exposure depends heavily on secret handling and configuration state.
Likely exposure
Most likely exposure is self-hosted or managed Strapi deployments using users-permissions with no explicit JWT algorithm configuration. Systems with well-protected jwtSecret values have materially lower practical risk.
Exploitation context
No KEV listing is provided, and the bundle does not cite active exploitation. Attackers need the jwtSecret before the described token minting is possible, making this a higher-precondition authentication weakness rather than a standalone remote takeover.
Researcher notes
The affected-version data in the bundle is incomplete, listing version "0" with defaultStatus unaffected. Rely on the CVE record, Strapi issue, PR, and advisory for precise product guidance. Do not assume broader Strapi components are affected.
Mitigation direction
- Check Strapi vendor guidance and the linked PR for fixed versions.
- Explicitly configure plugin::users-permissions.jwt.algorithm where supported.
- Rotate jwtSecret if exposure or improper access is suspected.
- Restrict and audit access to environment variables and secret stores.
- Prioritize updates for internet-facing Strapi applications using users-permissions.
Validation and detection
- Identify Strapi applications using the users-permissions plugin.
- Inspect configuration for plugin::users-permissions.jwt.algorithm.
- Confirm jwtSecret storage, access controls, and rotation history.
- Compare installed Strapi versions against vendor issue, PR, and advisory guidance.
- Review authentication logs for unexpected HS384 or HS512 JWT usage.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-327: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-57997 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N2.22.5VulnCheckVulnerability scoring details
Base CVSS 4.0 score
6.3MediumVector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
4.8MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Pull IssueCVE reference, VulnCheck · issue-tracking
- Pull IssueCVE reference, VulnCheck · issue-tracking
- Product DetailsCVE reference, VulnCheck · product
- https://www.vulncheck.com/advisories/strapi-users-permissions-jwt-algorithm-confusion-via-missing-algorithm-configurationCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of a Broken or Risky Cryptographic Algorithm
Use of a Broken or Risky Cryptographic Algorithm represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.