Filtered by vendor Strapi
Subscriptions
Total
28 CVE
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2023-39345 | 1 Strapi | 1 Strapi | 2024-09-04 | 7.6 High |
| 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 been addressed in version 4.13.1. Users are advised to upgrade. There are no known workarounds for this vulnerability. | ||||
| CVE-2019-19609 | 1 Strapi | 1 Strapi | 2024-08-05 | 7.2 High |
| The Strapi framework before 3.0.0-beta.17.8 is vulnerable to Remote Code Execution in the Install and Uninstall Plugin components of the Admin panel, because it does not sanitize the plugin name, and attackers can inject arbitrary shell commands to be executed by the execa function. | ||||
| CVE-2019-18818 | 1 Strapi | 1 Strapi | 2024-08-05 | 9.8 Critical |
| strapi before 3.0.0-beta.17.5 mishandles password resets within packages/strapi-admin/controllers/Auth.js and packages/strapi-plugin-users-permissions/controllers/Auth.js. | ||||
| CVE-2020-27664 | 1 Strapi | 1 Strapi | 2024-08-04 | 9.8 Critical |
| admin/src/containers/InputModalStepperProvider/index.js in Strapi before 3.2.5 has unwanted /proxy?url= functionality. | ||||
| CVE-2020-27665 | 1 Strapi | 1 Strapi | 2024-08-04 | 7.5 High |
| In Strapi before 3.2.5, there is no admin::hasPermissions restriction for CTB (aka content-type-builder) routes. | ||||
| CVE-2020-27666 | 1 Strapi | 1 Strapi | 2024-08-04 | 5.4 Medium |
| Strapi before 3.2.5 has stored XSS in the wysiwyg editor's preview feature. | ||||
| CVE-2020-13961 | 1 Strapi | 1 Strapi | 2024-08-04 | 6.5 Medium |
| Strapi before 3.0.2 could allow a remote authenticated attacker to bypass security restrictions because templates are stored in a global variable without any sanitation. By sending a specially crafted request, an attacker could exploit this vulnerability to update the email template for both password reset and account confirmation emails. | ||||
| CVE-2020-8123 | 1 Strapi | 1 Strapi | 2024-08-04 | 4.9 Medium |
| A denial of service exists in strapi v3.0.0-beta.18.3 and earlier that can be abused in the admin console using admin rights can lead to arbitrary restart of the application. | ||||
| CVE-2021-46440 | 1 Strapi | 1 Strapi | 2024-08-04 | 7.5 High |
| Storing passwords in a recoverable format in the DOCUMENTATION plugin component of Strapi before 3.6.9 and 4.x before 4.1.5 allows an attacker to access a victim's HTTP request, get the victim's cookie, perform a base64 decode on the victim's cookie, and obtain a cleartext password, leading to getting API documentation for further API attacks. | ||||
| CVE-2021-28128 | 1 Strapi | 1 Strapi | 2024-08-03 | 8.1 High |
| In Strapi through 3.6.0, the admin panel allows the changing of one's own password without entering the current password. An attacker who gains access to a valid session can use this to take over an account by changing the password. | ||||
| CVE-2022-32114 | 1 Strapi | 1 Strapi | 2024-08-03 | 8.8 High |
| 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 is supposed to be able to upload PDF files containing JavaScript, and that all files in a public assets folder are accessible to the outside world (unless the filename begins with a dot character). The administrator can choose to allow only image, video, and audio files (i.e., not PDF) if desired. | ||||
| CVE-2022-31367 | 1 Strapi | 1 Strapi | 2024-08-03 | 8.8 High |
| Strapi before 3.6.10 and 4.x before 4.1.10 mishandles hidden attributes within admin API responses. | ||||
| CVE-2022-30618 | 1 Strapi | 1 Strapi | 2024-08-03 | 7.5 High |
| 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-permissions). There are many scenarios in which such details from API users can leak in the JSON response within the admin panel, either through a direct or indirect relationship. Access to this information enables a user to compromise these users’ accounts if the password reset API endpoints have been enabled. In a worst-case scenario, a low-privileged user could get access to a high-privileged API account, and could read and modify any data as well as block access to both the admin panel and API by revoking privileges for all other users. | ||||
| CVE-2022-30617 | 1 Strapi | 1 Strapi | 2024-08-03 | 8.8 High |
| 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 authenticated user. For example, a low-privileged “author” role account can view these details in the JSON response for an “editor” or “super admin” that has updated one of the author’s blog posts. There are also many other scenarios where such details from other users can leak in the JSON response, either through a direct or indirect relationship. Access to this information enables a user to compromise other users’ accounts by successfully invoking the password reset workflow. In a worst-case scenario, a low-privileged user could get access to a “super admin” account with full control over the Strapi instance, and could read and modify any data as well as block access to both the admin panel and API by revoking privileges for all other users. | ||||
| CVE-2022-29894 | 1 Strapi | 1 Strapi | 2024-08-03 | 4.8 Medium |
| Strapi v3.x.x versions and earlier contain a stored cross-site scripting vulnerability in file upload function. By exploiting this vulnerability, an arbitrary script may be executed on the web browser of the user who is logging in to the product with the administrative privilege. | ||||
| CVE-2022-27263 | 1 Strapi | 1 Strapi | 2024-08-03 | 9.8 Critical |
| An arbitrary file upload vulnerability in the file upload module of Strapi v4.1.5 allows attackers to execute arbitrary code via a crafted file. | ||||
| CVE-2022-0764 | 1 Strapi | 1 Strapi | 2024-08-02 | 6.7 Medium |
| Arbitrary Command Injection in GitHub repository strapi/strapi prior to 4.1.0. | ||||
| CVE-2023-48218 | 1 Strapi | 1 Protected Populate | 2024-08-02 | 5.3 Medium |
| The Strapi Protected Populate Plugin protects `get` endpoints from revealing too much information. Prior to version 1.3.4, users were able to bypass the field level security. Users who tried to populate something that they didn't have access to could populate those fields anyway. This issue has been patched in version 1.3.4. There are no known workarounds. | ||||
| CVE-2023-38507 | 1 Strapi | 1 Strapi | 2024-08-02 | 7.3 High |
| 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 force attack increases. Version 4.12.1 has a fix for this issue. | ||||
| CVE-2023-37263 | 1 Strapi | 1 Strapi | 2024-08-02 | 6.8 Medium |
| Strapi is the an open-source headless content management system. Prior to version 4.12.1, field level permissions are not respected in the relationship title. If an actor has relationship title and the relationship shows a field they don't have permission to see, the field will still be visible. Version 4.12.1 has a fix for this issue. | ||||