Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
4 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
of CVE-2026-22706 Vulnerability Details - CVE: CVE-2026-22706 - CVSS v3.1 Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N (2.1 — Low) - Affected Versions: @strapi/admin and @strapi/plugin-users-permissions <=5.33.2 - How to Patch: Immediately update your Strapi to =5.33.3 Description of CVE-2026-22706 In Strapi versions prior to 5.33.3, changing or resetting a user's password did not invalidate the user's existing refresh-token sessions by default. The refresh-token invalidation step in the users-permissions and admin authentication controllers was conditional on a caller-supplied deviceId. When a password change or reset request did not include a deviceId, no refresh tokens were revoked, leaving every prior session active. An attacker who had previously obtained a refresh token could continue minting new access tokens after the legitimate user reset their password, allowing persistent unauthorized access for the lifetime of the refresh token (up to 30…
Recommended action: Upgrade to 5.33.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
In Strapi latest version, at function Settings - Webhooks, the application allows us to input a URL in order to create a Webook connection. However, we can input into this field the local domains such as localhost, 127.0.0.1, 0.0.0.0,.... in order to make the Application fetching into the internal itself, which causes the vulnerability Server - Side Request Forgery (SSRF). Payloads - http://127.0.0.1:80 - The Port is not open - http://127.0.0.1:1337 - The Port which Strapi is running on Steps to Reproduce - First of all, let's input the URL http://127.0.0.1:80 into the URL field, and click "Save". - Next, use the "Trigger" function and use Burp Suite to capture the request / response - The server return request to http://127.0.0.1/ failed, reason: connect ECONNREFUSED 127.0.0.1:80, BECAUSE the Port 80 is not open, since we are running Strapi on Port 1337, let's change the URL we input above into http://127.0.0.1:1337 - Continue to click the "Trigger" function, use Burp to…
Recommended action: Upgrade to 4.25.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
1. Summary There is a rate limit on the login function of Strapi's admin screen, but it is possible to circumvent it. 2. Details It is possible to avoid this by modifying the rate-limited request path as follows. 1. Manipulating request paths to upper or lower case. (Pattern 1) - In this case, avoidance is possible with various patterns. 2. Add path slashes to the end of the request path. (Pattern 2) 3. PoC Access the administrator's login screen (/admin/auth/login) and execute the following PoC on the browser's console screen. Pattern 1 (uppercase and lowercase) This PoC does the following: 1. Request 30 incorrect logins. 4. Execute the same request again and confirm that it is blocked by rate limit from the console screen. (429 Too Many Requests) 5. Next, falsify the pathname of the request (/admin/Login) and make a request again to confirm that it is possible to bypass the rate limit and log in. (200 OK) Pattern 2 (trailing slash) This PoC does the following: 1. Request 30…
Recommended action: Upgrade to 4.12.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
I can get access to user reset password tokens if I have the configure view permissions Details /content-manager/relations route does not remove private fields or ensure that they can't be selected PoC Install fresh strapi instance start up strapi and create an account create a new content-type give the content-type a relation with admin users and save go to Admin panel roles Author and then plugins. Enable for content-manager collection types the configure view In the collection time now only give them access to the collection you created for this. Create a new admin user account with the Author role Log out and request a password reset for the main admin user. Login on the newly created account go to the collection type you created for this test and click the create new entry button, click in the create new entry view on configure view. select the admin user relation we created click on resetPasswordToken Now go back to the create an entry view and when selection the…
Recommended action: Upgrade to 4.11.7 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.