{"id":"EUVD-2025-209860","enisaUuid":"c2c5ad11-a98e-3222-a5f5-32e8c9024b04","description":"Strapi is an open source headless content management system. In Strapi versions prior to 5.45.0, the rate-limit middleware in the users-permissions plugin derived its rate-limit key in part from `ctx.request.body.email`, including on routes whose body schema does not contain an `email` field (`/auth/local`, `/auth/reset-password`, `/auth/change-password`). An unauthenticated attacker could include an arbitrary `email` value in the request body to obtain a fresh rate-limit key per request, effectively bypassing per-IP throttling on those routes and enabling high-volume credential brute-force, password-reset code brute-force, and credential-stuffing attempts. The rate-limit key was constructed as `${userIdentifier}:${requestPath}:${ctx.request.ip}`, where `userIdentifier \u003d ctx.request.body.email`. On routes that legitimately use email as their identifier (e.g. `/auth/forgot-password`, `/auth/local/register`), this scoping is correct. On routes that use a different identifier (`identifier` for login, `code` for password reset, `currentPassword` for password change), the email field was not part of the route contract, but the middleware still incorporated it into the key, allowing a caller to rotate the value and obtain a unique key on every request. The patch in version 5.45.0 maintains an allow-list of routes that legitimately key on the email field and excludes that key component on every other route the middleware is mounted on. OAuth callback paths (`/connect/*`) are treated identifier-less. On routes outside the allow-list, the middleware now falls back to a fixed identifier-less key, ensuring per-IP throttling remains effective even when the request body is attacker-controlled.","datePublished":"May 14, 2026, 6:32:01 PM","dateUpdated":"May 16, 2026, 12:49:25 AM","baseScore":6.9,"baseScoreVersion":"4.0","baseScoreVector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","references":"https://github.com/strapi/strapi/security/advisories/GHSA-7mqx-wwh4-f9fw\nhttps://github.com/strapi/strapi/pull/24818\nhttps://github.com/strapi/strapi/commit/5e0d243cba9830e6f791de6a94798bcde51468db\nhttps://github.com/strapi/strapi/releases/tag/v5.45.0\n","aliases":"CVE-2025-64526\nGHSA-7mqx-wwh4-f9fw\n","assigner":"GitHub_M","epss":0.49,"enisaIdProduct":[{"id":"487f7211-e9be-301f-b236-996decc01e3e","product":{"name":"Strapi","vendor":{"name":"strapi"}},"product_version":"\u003c 5.45.0"},{"id":"8280008c-3117-3ef4-8997-2100d20ee3f6","product":{"name":"@strapi/plugin-users-permissions","vendor":{"name":"strapi"}},"product_version":"\u003c 5.45.0"}],"enisaIdVendor":[{"id":"9b48d8dc-4012-3fcb-b15c-7bd9b53e666b","vendor":{"name":"strapi"}}],"enisaIdVulnerability":[{"id":"575652e4-b5bf-3f46-97ce-fe76f925ca9c","vulnerability":{"id":"CVE-2025-64526","description":"Strapi is an open source headless content management system. In Strapi versions prior to 5.45.0, the rate-limit middleware in the users-permissions plugin derived its rate-limit key in part from `ctx.request.body.email`, including on routes whose body schema does not contain an `email` field (`/auth/local`, `/auth/reset-password`, `/auth/change-password`). An unauthenticated attacker could include an arbitrary `email` value in the request body to obtain a fresh rate-limit key per request, effectively bypassing per-IP throttling on those routes and enabling high-volume credential brute-force, password-reset code brute-force, and credential-stuffing attempts. The rate-limit key was constructed as `${userIdentifier}:${requestPath}:${ctx.request.ip}`, where `userIdentifier \u003d ctx.request.body.email`. On routes that legitimately use email as their identifier (e.g. `/auth/forgot-password`, `/auth/local/register`), this scoping is correct. On routes that use a different identifier (`identifier` for login, `code` for password reset, `currentPassword` for password change), the email field was not part of the route contract, but the middleware still incorporated it into the key, allowing a caller to rotate the value and obtain a unique key on every request. The patch in version 5.45.0 maintains an allow-list of routes that legitimately key on the email field and excludes that key component on every other route the middleware is mounted on. OAuth callback paths (`/connect/*`) are treated identifier-less. On routes outside the allow-list, the middleware now falls back to a fixed identifier-less key, ensuring per-IP throttling remains effective even when the request body is attacker-controlled.","datePublished":"May 14, 2026, 6:32:01 PM","dateUpdated":"May 16, 2026, 12:49:25 AM","status":"PUBLISHED","baseScore":6.9,"baseScoreVersion":"4.0","baseScoreVector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","references":"https://github.com/strapi/strapi/security/advisories/GHSA-7mqx-wwh4-f9fw\nhttps://github.com/strapi/strapi/pull/24818\nhttps://github.com/strapi/strapi/commit/5e0d243cba9830e6f791de6a94798bcde51468db\nhttps://github.com/strapi/strapi/releases/tag/v5.45.0\n","enisa_id":"EUVD-2025-209860\n","assigner":"GitHub_M","epss":0.49,"dataProcessed":"Oct 27, 2026, 7:20:28 AM","vulnerabilityProduct":[{"id":"076e2bb0-e51a-3dda-ae1c-3becb658e9dd","product":{"name":"Strapi","vendor":{"name":"strapi"}},"product_version":"\u003c 5.45.0"},{"id":"86cc161f-5c43-3ef4-a5a7-e2ba38c83c24","product":{"name":"@strapi/plugin-users-permissions","vendor":{"name":"strapi"}},"product_version":"\u003c 5.45.0"}],"vulnerabilityVendor":[{"id":"752484f0-47af-3edf-8635-a2a11f2fa970","vendor":{"name":"strapi"}}]}},{"id":"e8582792-3f62-3227-ab0a-6412e4de819b","vulnerability":{"id":"GHSA-7mqx-wwh4-f9fw","description":"Strapi has a rate limit bypass on users-permissions plugin via attacker-controlled email keying","datePublished":"May 13, 2026, 8:02:15 PM","dateUpdated":"May 15, 2026, 11:44:20 PM","baseScore":0.0,"references":"https://github.com/strapi/strapi/security/advisories/GHSA-7mqx-wwh4-f9fw\nhttps://nvd.nist.gov/vuln/detail/CVE-2025-64526\nhttps://github.com/strapi/strapi/pull/24818\nhttps://github.com/strapi/strapi/commit/5e0d243cba9830e6f791de6a94798bcde51468db\nhttps://github.com/strapi/strapi\nhttps://github.com/strapi/strapi/releases/tag/v5.45.0\n","enisa_id":"EUVD-2025-209860\n","aliases":"GHSA-7mqx-wwh4-f9fw\nCVE-2025-64526\n","epss":0.0,"dataProcessed":"Oct 25, 2026, 1:55:50 AM","vulnerabilityProduct":[],"vulnerabilityVendor":[]}}],"enisaIdAdvisory":[]}