Vulnerability in @strapi/plugin-users-permissions (CVE-2025-64526)
Summary
Vulnerability in @strapi/plugin-users-permissions (CVE-2025-64526). Risk of unauthorized operations or information disclosure. Exploitable via ctx.request.body.email. Mitigation: upgrade to 5.45.0 or later.
Original description
The description as published by the source.
Summary of CVE-2025-64526 Vulnerability Details
- CVE: CVE-2025-64526
- CVSS v3.1 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(6.9 — Medium) - Affected Versions:
@strapi/plugin-users-permissions<=5.44.0 - How to Patch: Immediately update your Strapi to >=5.45.0
Description of CVE-2025-64526
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…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-64526 has been found in @strapi/plugin-users-permissions.
Attackers can target a specific entry point like ctx.request.body.email over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade @strapi/plugin-users-permissions to 5.45.0 or later.
If unsure, ask your IT team or search "@strapi/plugin-users-permissions CVE-2025-64526" on the vendor's site.
CVE-2025-64526 (@strapi/plugin-users-permissions) — CWE-307 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: ctx.request.body.email / email / identifier / code
Patched: 5.45.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-307) exists in @strapi/plugin-users-permissions. Attackers reach the vulnerable code path via ctx.request.body.email without authentication.
Check the vendor advisory for the affected versions of @strapi/plugin-users-permissions. Attack surface: ctx.request.body.email / email / identifier / code.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 5.45.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@strapi/plugin-users-permissions' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@strapi/plugin-users-permissions' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@strapi/plugin-users-permissionsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @strapi/plugin-users-permissions to 5.45.0ステージング環境で 5.45.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- issue security-advisories@github.com
- package github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- web github.com