GHSA-8xx5-h6m3-jr33 CVE-2025-51586
Presta Shop vulnerable to email enumeration
- Severity
- 4.2 / 10
- Low · CVSS 3.1
- Exploit chance (EPSS)
- 0.82%
- Chance of exploitation in the next 30 days. Higher than 57.11% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-203 Observable Discrepancy
- CWE-359 Exposure of Private Personal Information to an Unauthorized Actor
- Fix
8.2.3- Upgrade prestashop/prestashop to this version or later
Description
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/
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| prestashop/prestashop | < 8.2.3 |
8.2.3 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
prestashop/prestashop Packagist → 8.2.3
- composer
composer require prestashop/prestashop:^8.2.3
Severity breakdown
CVSS 3.1 4.2
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
Weakness
CWE-203: Observable Discrepancy
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.
How to prevent it
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
- Implementation: Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success. If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files. Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.
CWE-359: Exposure of Private Personal Information to an Unauthorized Actor
The product does not properly prevent a person's private, personal information from being accessed by actors who either (1) are not explicitly authorized to access the information or (2) do not have the implicit consent of the person about whom the information is collected.
How to prevent it
- Requirements: Identify and consult all relevant regulations for personal privacy. An organization may be required to comply with certain federal and state regulations, depending on its location, the type of business it conducts, and the nature of any private data it handles. Regulations may include Safe Harbor Privacy Framework [REF-340], Gramm-Leach Bliley Act (GLBA) [REF-341], Health Insurance Portability and Accountability Act (HIPAA) [REF-342], General Data Protection Regulation (GDPR) [REF-1047], California Consumer Privacy Act (CCPA) [REF-1048], and others.
- Architecture and Design: Carefully evaluate how secure design may interfere with privacy, and vice versa. Security and privacy concerns often seem to compete with each other. From a security perspective, all important operations should be recorded so that any anomalous activity can later be identified. However, when private data is involved, this practice can in fact create risk. Although there are many ways in which private data can be handled unsafely, a common risk stems from misplaced trust. Programmers often trust the operating environment in which a program runs, and therefore believe that it is acceptable store private information on the file system, in the registry, or in other locally-controlled resources. However, even if access to certain resources is restricted, this does not guarantee that the individuals who do have access can be trusted.
- Implementation, Operation: Some tools can automatically analyze documents to redact, strip, or "sanitize" private information, although some human review might be necessary. Tools may vary in terms of which document formats can be processed. When calling an external program to automatically generate or convert documents, invoke the program with any available options that avoid generating sensitive metadata. Some formats have well-defined fields that could contain private data, such as Exchangeable image file format (Exif), which can contain potentially sensitive metadata such as geolocation, date, and time [REF-1515] [REF-1516].
References
Advisories
Packages
Other links
- github.com/PrestaShop/PrestaShop/security/advisories/GHSA-8xx5-h6m3-jr33
- github.com/PrestaShop/PrestaShop/commit/c97bdf10f77fedbe5a61a1dec5f96b3abb1d76fb
- build.prestashop-project.org/news/2025/prestashop-8-2-3-security-release
- github.com/PrestaShop/PrestaShop/releases/tag/8.2.1
- github.com/PrestaShop/PrestaShop/releases/tag/8.2.3
- maxime-morel.github.io/advisories/2025/CVE-2025-51586.md
- prestashop.com
- prestashop.com
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-w9f3-qc75-qgx9 PrestaShop has a stored XSS executable in customer service view | Critical | Also affects prestashop/prestashop |
| GHSA-35pf-37c6-jxjv PrestaShop has multiple stored XSS vulnerabilities via unprotected Template variables | Medium | Also affects prestashop/prestashop |
| GHSA-283w-xf3q-788v PrestaShop: Improper Use of Validation Framework | Medium | Also affects prestashop/prestashop |
| GHSA-67v7-3g49-mxh2 PrestaShop affected by time based enumeration in FO login form | Medium | Also affects prestashop/prestashop |
| GHSA-7pjr-2rgh-fc5g Anonymous PrestaShop customer can download other customers' invoices | Medium | Also affects prestashop/prestashop |
| GHSA-45vm-3j38-7p78 PrestaShop cross-site scripting via customer contact form in FO, through file upload | Medium | Also affects prestashop/prestashop |
| GHSA-3366-9287-7qpr Path disclosure in JavaScript variable | Medium | Also affects prestashop/prestashop |
| GHSA-vr7m-r9vm-m4wf PrestaShop XSS can be stored in DB from "add a message form" in order detail page (FO) | Medium | Also affects prestashop/prestashop |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor