CVE-2025-3930 Lack of JWT Expiration after Log Out in Strapi
Attackers can reuse stolen JWTs after logout or account deactivation, enabling persistent unauthorized access to Strapi admin interfaces.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-3930?
CVE-2025-3930 is a medium-severity vulnerability in Strapi, published on 16 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-613
Which versions are affected by CVE-2025-3930?
2 open source packages ship an affected version, including @strapi/strapi.
| Package | Affected | Fixed in |
|---|---|---|
@strapi/strapi npm | All versions | 5.24.1 |
@strapi/strapi npm | All versions | 5.24.1 |
How do I fix CVE-2025-3930?
Upgrade @strapi/strapi to 5.24.1 or later.
Is CVE-2025-3930 being exploited?
There is no known exploitation of CVE-2025-3930 in the wild and no public exploit code.
Sources
Also known as GHSA-4r8w-3jww-m2rp.