cve.bz

CVE-2025-3930 strapi strapi: Insufficient Session Expiration

6.3 mediumEPSS 0.7%Fix available

Medium (6.3) in strapi strapi. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in @strapi/strapi 5.24.1.

On this page
Strapi uses JSON Web Tokens (JWT) for authentication. After logout or account deactivation, the JWT is not invalidated, which allows an attacker who has stolen or intercepted the token to freely reuse it until its expiration date (which is set to 30 days by default, but can be changed). The existence of /admin/renew-token endpoint allows anyone to renew near-expiration tokens indefinitely, further increasing the impact of this attack. This issue has been fixed in version 5.24.1.

Severity

CVSS 4.0

6.3 medium
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
EPSS
0.7% (unchanged from 0.7% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 54th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-613 Insufficient Session Expiration deprecated by MITRE see CWE-1463, CWE-1464
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • @strapi/strapi (npm): fixed in 5.24.1

Ask an AI about this CVE

Show the promptExplain CVE-2025-3930 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-3930?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-3930?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-3930 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Strapibefore 5.24.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-4r8w-3jww-m2rpnpm@strapi/strapi<5.24.15.24.1

References

Check your stackJSON