dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-62945

HIGH · 7.1 CVSS v3.1 Published 2025-10-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Cross-Site Request Forgery (CSRF) vulnerability in Eduard Pinuaga Linares Did Prestashop Display did-prestashop-display allows Stored XSS.This issue affects Did Prestashop Display: from n/a through <= 1.0.30.

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Did Prestashop Display module allows attackers to craft malicious requests that result in stored Cross-Site Scripting (XSS). The lack of anti-CSRF tokens on form submissions enables attackers to trick authenticated administrators into triggering stores XSS payloads that persist in the application.

MitigationImplement anti-CSRF tokens on all form submissions and state-changing operations, combined with proper input validation and output encoding to prevent stored XSS. Update to the latest module version if available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Locate the Did Prestashop Display module
    In your PrestaShop installation, navigate to the modules directory (usually /modules/) and search for a folder named 'didprestashopdisplay', 'did', or similar. Also check the PrestaShop admin panel under Modules > Module Manager for an installed module named 'Did Prestashop Display' or 'Did Display'.
    Affected if The module is installed and present in the PrestaShop modules directory.
  2. Check the module version
    Open the main PHP file of the module (usually index.php or a file named after the module) and look for a version definition (often $this->version = 'x.x.x'; or similar). Compare this version to any official release notes or changelogs from the module developer.
    Affected if You cannot determine the version OR the installed version is older than the latest available version from the developer.
  3. Inspect form handling code for CSRF tokens
    In the module's PHP files, examine any form handling functions (processSubmit, saveConfig, updateSettings, postProcess, etc.). Search for occurrences of 'csrf' or 'token' in the code. Check if form submissions validate a token before processing.
    Affected if Form handling code does not reference, validate, or require any CSRF token or security token before processing administrator requests.
  4. Check admin forms for token input fields
    In the module's admin controller or template files (.tpl), examine form definitions. Look for {hook h='displayAdminForm'} or similar, and verify that forms contain an input field with type='hidden' containing a token value (such as <input type="hidden" name="token" value="...">).
    Affected if Admin forms generated by this module do not include a hidden token or security token field.
  5. Look for stored XSS in module data
    Query your PrestaShop database for any content stored by this module. Check tables related to the module (often named ps_did_* or similar). Inspect configuration values in ps_configuration table for the module. Look for suspicious script tags, <img onerror=, or javascript: URIs in stored values.
    Affected if The module's database tables or configuration contain unexpected HTML, script tags, or javascript: handlers that were not intentionally added by your administrators.

Your environment is affected if the Did Prestashop Display module is installed AND its forms lack CSRF token validation AND you observe suspicious stored content in module data.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens on all form submissions and state-changing operations, combined with proper input validation and output encoding to prevent stored XSS. Update to the latest module version if available.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62945 — 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-2025-62945 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