PrestashopCMS
CVE-2026-25597
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPrestaShop is an open source e-commerce web application. Prior to 8.2.4 and 9.0.3, there is a time-based user enumeration vulnerability in the user authentication functionality of PrestaShop. This vulnerability allows an attacker to determine whether a customer account exists in the system by measuring response times. This vulnerability is fixed in 8.2.4 and 9.0.3.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencePrestaShop versions prior to 8.2.4 and 9.0.3 contain a time-based user enumeration vulnerability in the customer authentication functionality. Attackers can determine whether a customer account exists by measuring subtle response time differences between authentication attempts for valid versus invalid usernames. This information disclosure enables targeted attacks such as credential stuffing or phishing campaigns.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
PrestashopCMS
< 8.2.4>= 9.0.0, < 9.0.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed PrestaShop versionLog into the PrestaShop admin dashboard and navigate to Advanced Parameters > Configuration Information, or check the 'ps_version' value in the database or the 'app/config parameters.php' fileAffected if The installed version is less than 8.2.4, or is 9.0.0, 9.0.1, or 9.0.2
-
Verify customer authentication is enabledConfirm that the customer (front-end) login functionality is active on the shop. Check via the PrestaShop back office under Shop Parameters > Customer Settings > Customer options, or verify that the authentication controller is accessible at the /login routeAffected if Customer authentication is enabled and accessible to unauthenticated users
-
Identify the authentication controllerLocate the file controllers/front/AuthController.php or similar authentication-related controllers in the PrestaShop installationAffected if The authentication controller exists and handles login requests
-
Check for time-based response consistencyTest the customer login endpoint by sending authentication requests with both valid and invalid usernames, measuring the response time for each. Compare whether response times differ noticeably between valid and invalid accountsAffected if Response times noticeably differ between valid and invalid usernames, indicating the enumeration vulnerability is present
-
Verify compensating control statusReview the authentication code or web server configuration to determine if response timing has been artificially equalized (consistent timing regardless of account validity)Affected if No consistent timing mitigation has been implemented and the version is vulnerable
You are affected if your PrestaShop installation version is below 8.2.4 or between 9.0.0 and 9.0.2 inclusive, and the customer authentication feature is enabled with no consistent response timing mitigation in place.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped8.2.49.0.3
Upgrade PrestaShop to version 8.2.4 or 9.0.3 or later. As a compensating control, implement consistent response timing for all authentication attempts regardless of account existence to mitigate enumeration before patching.
Upgrade to PrestaShop 8.2.4 (if on 8.x) or 9.0.3 (if on 9.x)
- 1. Create a full backup of the PrestaShop database and all files
- 2. Enable maintenance mode to prevent user access during upgrade
- 3. Download the fixed version (8.2.4 for 8.x branches or 9.0.3 for 9.x branches) from the official PrestaShop releases page
- 4. Extract the downloaded package and upload all files to the server, overwriting existing files while preserving the /app/config/parameters.php configuration file
- 5. Delete the cache by clearing all contents in /var/cache/ (or /cache/ depending on version)
- 6. Run the PrestaShop upgrade script by accessing /install/ or /admin/ upgrade functionality
- 7. Verify the upgrade completed successfully by checking the PrestaShop version in the back office
- 8. Test user authentication to confirm the time-based enumeration vulnerability is fixed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Prestashop
Scoped from the published advisory
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25597 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-25597 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data