How severe is GHSA-4r8w-3jww-m2rp?

No CVSS score has been assigned to GHSA-4r8w-3jww-m2rp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4r8w-3jww-m2rp?

GHSA-4r8w-3jww-m2rp affects the following packages: @strapi/strapi (npm). Ecosystems affected: npm.

How do I fix GHSA-4r8w-3jww-m2rp?

Update @strapi/strapi to 5.24.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4r8w-3jww-m2rp is resolved across your whole dependency graph.

How do I detect GHSA-4r8w-3jww-m2rp in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @strapi/strapi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-4r8w-3jww-m2rp if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-4r8w-3jww-m2rp actively exploited in the wild?

No public exploit code has been indexed for GHSA-4r8w-3jww-m2rp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-4r8w-3jww-m2rp?

GHSA-4r8w-3jww-m2rp has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 53th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-4r8w-3jww-m2rp?

GHSA-4r8w-3jww-m2rp is classified as CWE-613 (CWE-613). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-4r8w-3jww-m2rp published, and has it been updated?

GHSA-4r8w-3jww-m2rp was published on October 16, 2025 and was last updated on October 22, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Strapi is vulnerable to Insufficient Session Expiration

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-4r8w-3jww-m2rp.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs53th percentile — riskier than 53% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

108other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@strapi/strapinpm

271Kdownloads / week

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@strapi/strapi`	all versions	5.24.1`npm install @strapi/strapi@5.24.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @strapi/strapi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @strapi/strapi to 5.24.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4r8w-3jww-m2rp is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-4r8w-3jww-m2rp in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

Strapi is vulnerable to Insufficient Session ExpirationGHSA-4r8w-3jww-m2rp