← Back
CVE-2025-64526
medium
CVSS 5.3
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**A vulnerability** (CWE-307) exists in @strapi/plugin-users-permissions. Attackers reach the vulnerable code path via ``ctx.request.body.email`` without authentication.
📍 Affected scope
@strapi/plugin-users-permissions — . Attack surface: `ctx.request.body.email` / `email` / `identifier` / `code`.
🔥 Severity
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5.45.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @strapi/plugin-users-permissions to 5.45.0ステージング環境で 5.45.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@strapi/plugin-users-permissions
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"5.45.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-64526
- package https://github.com/strapi/strapi
- web https://github.com/strapi/strapi/security/advisories/GHSA-7mqx-wwh4-f9fw
- web https://github.com/strapi/strapi/pull/24818
- web https://github.com/strapi/strapi/commit/5e0d243cba9830e6f791de6a94798bcde51468db
- web https://github.com/strapi/strapi/releases/tag/v5.45.0
- web https://github.com/advisories/GHSA-7mqx-wwh4-f9fw