Strapi vulnerabilities
We track 18 vulnerabilities in Strapi products across 3 products. 17 are rated high or critical, and 1 has been exploited in real attacks. The most recent was published on October 27, 2026.
Latest Strapi vulnerabilities
- 9.1 Critical severity
Strapi Open Source and Enterprise Headless CMS: Missing Authorization
The strapi/review-workflows package is vulnerable to a broken access control vulnerability allowing updates to be made without verifying whether the caller possesses update rights for the underlying document.
- 8.7 High severity
strapi: Improper Neutralization of Input During Web Page Generation
Strapi versions 4.x through 4.26.2 and 5.x before 5.48.1 contain a stored cross-site scripting vulnerability in the content manager WYSIWYG preview component that fails to strip script tags from rich text. An Author-role user can store malicious script tags in
- 7.5 High severity
strapi: Improper Limitation of a Pathname to a Restricted Directory
Strapi is an open source headless content management system. Strapi versions starting in 4.0.0 and prior to 5.37.0 did not sufficiently sanitize query parameters when filtering content via relational fields. An unauthenticated attacker could use the `where` qu
- 7.2 High severity
strapi: Improper Neutralization of Special Elements used in an SQL Command
Strapi is an open source headless content management system. In versions on the 4.x branch prior to 4.26.1 and on the 5.x branch prior to 5.33.2, a database-query injection vulnerability existed in the Strapi Content-Type Builder write API. An authenticated ad
- 8.2 High severity
strapi: Authorization Bypass Through User-Controlled Key
Strapi is an open-source headless content management system. In versions from 5.0.0 to before 5.5.2, the lookup operator provided by the document service does not properly sanitize query parameters for private fields. An attacker can access private fields, inc
- 7.5 High severity
strapi: Server-Side Request Forgery
Strapi is an open-source content management system. Prior to version 4.25.2, inputting a local domain into the Webhooks URL field leads to the application fetching itself, resulting in a server side request forgery (SSRF). This issue has been patched in versio
- 8.6 High severity
strapi: Server-Side Request Forgery
Strapi v4.24.4 was discovered to contain a Server-Side Request Forgery (SSRF) via the component /strapi.io/_next/image. This vulnerability allows attackers to scan for open ports or access sensitive information via a crafted GET request. NOTE: The Strapi Devel
- 8.1 High severity
strapi: Authentication Bypass by Capture-replay
Strapi is an open-source content management system. By combining two vulnerabilities (an `Open Redirect` and `session token sent as URL query parameter`) in @strapi/plugin-users-permissions before version 4.24.2, is its possible of an unauthenticated attacker
- 7.5 High severity
strapi: Improper Authentication
strapi is an open-source headless CMS. Versions prior to 4.13.1 did not properly restrict write access to fielded marked as private in the user registration endpoint. As such malicious users may be able to errantly modify their user records. This issue has bee
- 9.8 Critical severity
strapi: Allocation of Resources Without Limits or Throttling
Strapi is the an open-source headless content management system. Prior to version 4.12.1, there is a rate limit on the login function of Strapi's admin screen, but it is possible to circumvent it. Therefore, the possibility of unauthorized login by login brute
- 7.5 High severity
strapi: Exposure of Sensitive Information to an Unauthorized Actor
Strapi is an open-source headless content management system. Prior to version 4.10.8, it is possible to leak private fields if one is using the `t(number)` prefix. Knex query allows users to change the default prefix. For example, if someone changes the prefix
- 7.1 High severity
strapi: Exposure of Sensitive Information to an Unauthorized Actor
Strapi is an open-source headless content management system. Prior to version 4.10.8, anyone (Strapi developers, users, plugins) can make every attribute of a Content-Type public without knowing it. The vulnerability only affects the handling of content types
- 4.9 Medium severity
Strapi Cleartext Storage of Sensitive Information Exploited
Strapi through 4.5.5 allows attackers (with access to the admin panel) to discover sensitive user details by exploiting the query filter. The attacker can filter users by columns that contain sensitive information and infer a value from API responses. If the a
- 7.5 High severity
Strapi: Improper Authentication
Strapi through 4.5.5 does not verify the access or ID tokens issued during the OAuth flow when the AWS Cognito login provider is used for authentication. A remote attacker could forge an ID token that is signed using the 'None' type algorithm to bypass authent
- 7.2 High severity
Strapi: Improper Neutralization of Special Elements in Output Used by a Downstream Component
Strapi through 4.5.5 allows authenticated Server-Side Template Injection (SSTI) that can be exploited to execute arbitrary code on the server. A remote attacker with access to the Strapi admin panel can inject a crafted payload that executes code on the server
- 8.8 High severity
Strapi: Unrestricted Upload of File with Dangerous Type
An unrestricted file upload vulnerability in the Add New Assets function of Strapi 4.1.12 allows attackers to conduct XSS attacks via a crafted PDF file. NOTE: the project documentation suggests that a user with the Media Library "Create (upload)" permission i
- 7.5 High severity
Strapi: Improper Removal of Sensitive Information Before Storage or Transfer
An authenticated user with access to the Strapi admin panel can view private and sensitive data, such as email and password reset tokens, for API users if content types accessible to the authenticated user contain relationships to API users (from:users-permiss
- 8.8 High severity
Strapi: Improper Removal of Sensitive Information Before Storage or Transfer
An authenticated user with access to the Strapi admin panel can view private and sensitive data, such as email and password reset tokens, for other admin panel users that have a relationship (e.g., created by, updated by) with content accessible to the authent