CVE-2025-51586: account enumeration in PrestaShop — back-office employee password reset

If you run a PrestaShop store, there is a big difference between running older software and being exposed to a particular vulnerability. CVE-2025-51586 concerns back-office employee password reset. Here is what was reported, which technical conditions matter and how to fix the issue without turning a maintenance task into a production incident.

What happened?

Manipulating id_employee and reset_token in the back-office password-reset flow could reveal employee email addresses.

The issue was reported in functionality associated with the PrestaShop application. Whether the entry point is reachable, the required privileges and local configuration can significantly change exposure.

The technical details: how this vulnerability works

Information leaks are not always explicit. Different messages or small timing variations in authentication can reveal whether an email exists. Repeated at scale, this makes account lists for phishing or password-reuse attacks easier to build.

Generic responses, similar processing for existing and nonexistent accounts, rate limits and monitoring repeated attempts help. Enumeration on its own does not prove an account has been taken over.

The precise entry point is back-office employee password reset, not ordinary customer login. Someone who already knew the back-office URL could manipulate id_employee and reset_token to infer staff email addresses. 8.2.3 fixed the issue. This can support targeted phishing, but it does not imply that passwords were disclosed.

What is the real impact?

Under the relevant conditions, the issue may allow discovering which accounts exist, which can support phishing and abusive login attempts. That does not establish that a store has been compromised, nor does it mean every installation is exploitable in the same way. Severity in practice depends on versions, configuration, authentication requirements and server privileges.

Also distinguish a vulnerability in the PrestaShop core from a vulnerability in a third-party module. The presence of a vulnerable extension is not implied merely by using PrestaShop.

Which versions are affected?

• Component: back-office employee password reset
• Reported affected versions: before 8.2.3
• Fixed version: 8.2.3
• Advisory publication: 2025-09-04

Treat this as an initial assessment. Custom overrides, local patches and modified distributions mean the back-office version number might not describe every file currently deployed.

How do you fix CVE-2025-51586?

1. Inventory the installation. Record the PrestaShop version, module version where applicable and PHP environment. Confirm whether back-office employee password reset is present.
2. Check affected versions. The record lists before 8.2.3. Verify these details against the maintainer's notice because configuration requirements can narrow exposure.
3. Create a full backup. Include files, database and configuration, and test the change in staging whenever possible.
4. Apply the remediation. The documented patched version is 8.2.3. If you run a newer branch, verify that its release includes the fix and that any involved modules are also current.
5. Regression-test critical workflows. Check login, cart, checkout, customer area, back office, email and store integrations.
6. Review prior exposure. A successful patch does not by itself establish whether the issue was previously exploited.

How can I check for exploitation attempts?

Review authentication, back-office and API logs for unusual calls to the relevant endpoint. Cross-check the effective permissions and actions recorded for each account. Preserve evidence before changing a potentially compromised system.

Cloudflare or another WAF may reduce some exploit attempts, but it does not patch vulnerable application code.

Developer review checklist

Start code review at the affected component above. Trace input from HTTP (Tools::getValue(), AJAX handlers, uploads or headers) into the sensitive operation and confirm server-side validation at that boundary. Also check custom overrides and in-house modules so the same unsafe pattern is not reintroduced after installing the official patch.

Want someone to handle the update?

A safe remediation is more than clicking an update button. Dependencies need reviewing, rollback must be possible, the right patch must be deployed and key business flows should continue working.

Would you like me to review and fix this vulnerability in your PrestaShop store? I can inspect your versions and modules, assess exposure, apply the appropriate security changes and regression-test key workflows. Get in touch and we can handle it calmly, without unnecessary alarm.

Editorial note: this article summarizes publicly available information and does not prove your shop was exploited. Whenever a patched version could not be verified, that limitation is explicitly stated.