Vulnerability in prestashop/prestashop (CVE-2025-51586)
Summary
Vulnerability in prestashop/prestashop (CVE-2025-51586). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 8.2.3 or later.
Original description
The description as published by the source.
Impact
An unauthenticated attacker with access to the back-office URL can manipulate the id_employee and reset_token parameters to enumerate valid back-office employee email addresses.
Impacted parties:
Store administrators and employees: their email addresses are exposed.
Merchants: risk of phishing, social engineering, and brute-force attacks targeting admin accounts.
Patches
PrestaShop 8.2.3
Workarounds
You must upgrade, or at least apply the changes from the PrestaShop 8.2.3 patch. More information: https://build.prestashop-project.org/news/2025/prestashop-8-2-3-security-release/
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-51586 has been found in prestashop/prestashop.
Risk of unauthorized operations or information disclosure.
What to do: upgrade prestashop/prestashop to 8.2.3 or later.
If unsure, ask your IT team or search "prestashop/prestashop CVE-2025-51586" on the vendor's site.
CVE-2025-51586 (prestashop/prestashop) — CWE-203
Attack vector: remote (network-reachable) / no user interaction
Patched: 8.2.3 — apply immediately
Workaround: You must upgrade, or at least apply the changes from the PrestaShop 8.2.3 patch.
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-203) exists in prestashop/prestashop.
Check the vendor advisory for the affected versions of prestashop/prestashop.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 8.2.3.
Workaround: You must upgrade, or at least apply the changes from the PrestaShop 8.2.3 patch.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'prestashop/prestashop' . 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 'prestashop/prestashop' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
prestashop/prestashopを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
You must upgrade, or at least apply the changes from the PrestaShop 8.2.3 patch.パッチが適用されるまでの応急処置として、You must upgrade, or at least apply the changes from the PrestaShop 8.2.3 patch. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade prestashop/prestashop to 8.2.3ステージング環境で 8.2.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web build.prestashop-project.org
- web github.com
- web github.com
- web maxime-morel.github.io
- web prestashop.com