dbcve.org
PrestashopCMS

CVE-2023-25170

HIGH · 8.8 CVSS v3.1 Published 2023-03-13
Fix available
A fix is available. Upgrade to 8.0.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
PrestaShop is an open source e-commerce web application that, prior to version 8.0.1, is vulnerable to cross-site request forgery (CSRF). When authenticating users, PrestaShop preserves session attributes. Because this does not clear CSRF tokens upon login, this might enable same-site attackers to bypass the CSRF protection mechanism by performing an attack similar to a session-fixation. The problem is fixed in version 8.0.1.

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 confidence

PrestaShop prior to 8.0.1 is vulnerable to CSRF due to session attributes being preserved during user authentication without clearing CSRF tokens upon login. This enables same-site attackers to perform session-fixation-like attacks to bypass CSRF protection mechanisms.

MitigationUpgrade PrestaShop to version 8.0.1 or later, which implements proper CSRF token clearing upon login.

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
Affected:< 8.0.1

CVSS 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed PrestaShop version
    Locate the version file (typically app/AppKernel.php or config/version.php) or access the back office Dashboard > Information page to view the PrestaShop version number
    Affected if The installed version is any release prior to 8.0.1 (for example, 8.0.0, 1.7.8.x, 1.7.7.x, etc.)
  2. Verify session handling behavior
    Examine the authentication/login controller code in controllers/admin/AdminLoginController.php or similar login handling files. Look for session regeneration or CSRF token clearing logic executed after successful authentication
    Affected if The login process does not clear or regenerate session attributes including CSRF tokens upon successful user login
  3. Confirm session-based authentication is in use
    Check if the PrestaShop installation uses PHP session-based authentication (session_start() and $_SESSION usage) rather than stateless token-based auth. Inspect authcookie or cookie encryption configuration in config/settings.inc.php
    Affected if The application relies on PHP session storage and session attributes are persisted across login/logout cycles without being cleared

You are affected if your PrestaShop installation version is below 8.0.1 AND the login process preserves session attributes without clearing CSRF tokens.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 8.0.1 or later
Fixed in 8.0.1
Interim mitigation

Upgrade PrestaShop to version 8.0.1 or later, which implements proper CSRF token clearing upon login.

Recommended fix High confidence

8.0.1

  1. Create a complete backup of the current PrestaShop installation including files and database
  2. Place the site in maintenance mode to prevent user access during upgrade
  3. Download PrestaShop version 8.0.1 from the official source
  4. Upload and extract the new version files to the server, overwriting existing files
  5. Run any provided upgrade script or allow the automated upgrade process to complete
  6. Update modules and themes to versions compatible with PrestaShop 8.0.1 if needed
  7. Test critical e-commerce functions (checkout, login, admin access) to verify proper operation
  8. Remove maintenance mode and monitor for any issues
Caveat Review module and theme compatibility before upgrading, as some third-party addons may require updates for PrestaShop 8.x

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Prestashop Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25170 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-25170 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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