SQL injection vulnerability in KnowBand Module One Page Checkout, Social Login & Mailchimp (supercheckout) v.8.0.3 and before allows a remote attacker to execute arbitrary code via a crafted request to the updateCheckoutBehaviour function in the supercheckout.php component.

**IMPORTANT NOTICE**: DO NOT REPORT VULNERABILITIES SOLELY TO THE AUTHOR OR MARKETPLACE.

We urge you to report any vulnerabilities directly to us. Our mission is to ensure the safety and security of the PrestaShop ecosystem. Unfortunately, many module developers may not always recognize or acknowledge the vulnerabilities in their code, whether due to lack of awareness, or inability to properly evaluate the associated risk, or other reasons.

Given the rise in professional cybercrime networks actively seeking out these vulnerabilities, it's crucial that any potential threats are promptly addressed and the community is informed. The most effective method to do this is by publishing a CVE, like the one provided below.

Should you discover any vulnerabilities, **please report them to us at: report\[@\]security-presta.org**.

Every vulnerability report helps make the community more secure, and we are profoundly grateful for any information shared with us.

In the module “Module One Page Checkout, Social Login & Mailchimp” (supercheckout) up to version 8.0.3 from KnowBand for PrestaShop, an anonymous user can perform a SQL injection.

**Summary**

*   **CVE ID**: CVE-2023-44024
*   **Published at**: 2023-10-05
*   **Platform**: PrestaShop
*   **Product**: supercheckout
*   **Impacted release**: <= 8.0.3 (8.0.4 fixed the vulnerability)
*   **Product author**: KnowBand
*   **Weakness**: CWE-89
*   **Severity**: critical (9.8)

**Description**

The method SupercheckoutSupercheckoutModuleFrontController::updateCheckoutBehaviour() has sensitive SQL calls that can be executed with a trivial http call and exploited to forge a SQL injection.

**WARNING** : This exploit is actively used to deploy a webskimmer to massively steal credit cards.

This exploit uses a PrestaShop front controller and most attackers can conceal the module controller’s path during the exploit, so you will never know within your conventional frontend logs that it exploits this vulnerability. **You will only see “POST /” inside your conventional frontend logs.** Activating the AuditEngine of mod\_security (or similar) is the only way to get data to confirm this exploit.

**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**

*   Obtain admin access
*   Remove data from the associated PrestaShop
*   Copy/paste data from sensitive tables to FRONT to expose tokens and unlock admins’s ajax scripts
*   Rewrite SMTP settings to hijack emails

**Patch from 8.0.3**

    --- 8.0.3/modules/supercheckout/controllers/front/supercheckout.php
    +++ 8.0.4/modules/supercheckout/controllers/front/supercheckout.php
    private static function transactionExists(string
    ...
            if (isset($result) && !empty($result) && $result != "") {
                //check if column exists or not
                $check_col_sql = 'SELECT count(*) FROM information_schema.COLUMNS
    -                              WHERE COLUMN_NAME = "' . $field_name . '"
    +                              WHERE COLUMN_NAME = "' . pSQL($field_name) . '"
                                   AND TABLE_NAME = "' . _DB_PREFIX_ . 'kb_checkout_behaviour_stats"
                                   AND TABLE_SCHEMA = "' . _DB_NAME_ . '"';
                $check_col = Db::getInstance(_PS_USE_SQL_SLAVE_)->getValue($check_col_sql);
                if ($check_col == 1) {
    -               $sql = 'UPDATE ' . _DB_PREFIX_ . 'kb_checkout_behaviour_stats SET ' . pSQL($field_name) . ' = ' . (int) $filled . ' WHERE id_cart = ' . (int) $this->context->cart->id;
    +               $sql = 'UPDATE ' . _DB_PREFIX_ . 'kb_checkout_behaviour_stats SET `' . bqSQL($field_name) . '` = ' . (int) $filled . ' WHERE id_cart = ' . (int) $this->context->cart->id;
                    Db::getInstance()->execute($sql);
                    if ((Tools::getValue('use_for_invoice') == 'true' || Tools::getValue('use_for_invoice') == true) && $field_name != 'email' && (strpos($field_name, '_invoice') == false)) {
    -                   $sql = 'UPDATE ' . _DB_PREFIX_ . 'kb_checkout_behaviour_stats SET ' . pSQL($field_name) . '_invoice = ' . (int) $filled . ' WHERE id_cart = ' . (int) $this->context->cart->id;
    +                   $sql = 'UPDATE ' . _DB_PREFIX_ . 'kb_checkout_behaviour_stats SET `' . bqSQL($field_name) . '_invoice` = ' . (int) $filled . ' WHERE id_cart = ' . (int) $this->context->cart->id;
                        Db::getInstance()->execute($sql);
                    }
                }
    

**Other recommendations**

*   It’s recommended to upgrade to the latest version of the module **supercheckout**.
*   Upgrade PrestaShop to the latest version to disable multiquery executions (separated by “;”) - be warned that this functionality **WILL NOT** protect your SHOP against injection SQL which uses the UNION clause to steal data.
*   Change the default database prefix ps_ with a new longer, arbitrary prefix. Nevertheless, be warned that this is useless against blackhats with DBA senior skills 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 this set of rules.

**Timeline**

Date

Action

2023-07-24

Issue discovered during a code review by TouchWeb.fr

2023-07-24

Contact PrestaShop Addons security Team to confirm version scope

2023-07-25

PrestaShop Addons security Team to confirm version scope

2023-09-19

Author provide a patch

2023-09-22

Request a CVE ID

2023-09-28

Received CVE ID

2023-10-05

Publish this security advisory

**Links**

*   PrestaShop addons product page
*   National Vulnerability Database

**DISCLAIMER:** _The French Association Friends Of Presta (FOP) acts as an intermediary to help hosting this advisory. While we strive to ensure the information and advice provided are accurate, FOP cannot be held liable for any consequences arising from reported vulnerabilities or any subsequent actions taken._

CVE-2023-44024: [CVE-2023-44024] Improper neutralization of SQL parameters in KnowBand - One Page Checkout, Social Login & Mailchimp module for PrestaShop

Presto Changeo attributegrid up to 2.0.3 was discovered to contain a SQL injection vulnerability via the component disable_json.php.

**IMPORTANT NOTICE**: DO NOT REPORT VULNERABILITIES SOLELY TO THE AUTHOR OR MARKETPLACE.

We urge you to report any vulnerabilities directly to us. Our mission is to ensure the safety and security of the PrestaShop ecosystem. Unfortunately, many module developers may not always recognize or acknowledge the vulnerabilities in their code, whether due to lack of awareness, or inability to properly evaluate the associated risk, or other reasons.

Given the rise in professional cybercrime networks actively seeking out these vulnerabilities, it's crucial that any potential threats are promptly addressed and the community is informed. The most effective method to do this is by publishing a CVE, like the one provided below.

Should you discover any vulnerabilities, **please report them to us at: report\[@\]security-presta.org**.

Every vulnerability report helps make the community more secure, and we are profoundly grateful for any information shared with us.

In the module “Attribute Grid” (attributegrid) from Presto Changeo for PrestaShop, a guest can perform SQL injection in affected versions.

**Summary**

*   **CVE ID**: CVE-2023-43983
*   **Published at**: 2023-10-03
*   **Platform**: PrestaShop
*   **Product**: attributegrid
*   **Impacted release**: < 2.0.3 \[SEE NOTE BELOW\]
*   **Product author**: Presto Changeo
*   **Weakness**: CWE-89
*   **Severity**: critical (9.8)

**Description**

Ajax scripts disable\_json.php has sensitive SQL calls that can be executed with a trivial http call and exploited to forge a SQL injection.

Note : Author refuse to help us to fix the version scope since its module are no longer supported. This vulnerability has been seen in versions up to version 1.6.7 and no longer exists in version 2.0.3. We do not have versions > 1.6.7 and < 2.0.3, so it’s impossible for us to certify that these versions are or not are impacted by this vulnerability.

**WARNING** : Author discontinue support of its module so you should no longer continue to use them.

**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**

*   Obtain admin access
*   Remove data from the associated PrestaShop
*   Copy/paste data from sensitive tables to FRONT to expose tokens and unlock admins’s ajax scripts
*   Rewrite SMTP settings to hijack emails

**Patch from 1.6.7**

    --- 1.6.7/modules/attributegrid/disable_json.php
    +++ XXXXX/modules/attributegrid/disable_json.php
    ...
    		LEFT JOIN `'._DB_PREFIX_.'product_attribute_combination` pac ON pac.`id_product_attribute` = pa.`id_product_attribute`
    		'.($ps_version >= 1.5?Shop::addSqlAssociation('product_attribute', 'pa'):'').'
    -		WHERE pa.`id_product` in ('.$_POST['products'].')';
    +		WHERE pa.`id_product` in ('.implode(',', array_map('intval', explode(',', $_POST['products']))).')';
    

**Other recommendations**

*   It’s recommended to upgrade to the latest version of the module **attributegrid**.
*   Upgrade PrestaShop to the latest version to disable multiquery executions (separated by “;”) - be warned that this functionality **WILL NOT** protect your SHOP against injection SQL which uses the UNION clause to steal data.
*   Change the default database prefix ps_ with a new longer, arbitrary prefix. Nevertheless, be warned that this is useless against blackhats with DBA senior skills 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 this set of rules.

**Timeline**

Date

Action

2023-08-01

Issue discovered during a code review by TouchWeb.fr

2023-08-01

Contact Author to confirm versions scope by author

2023-08-01

Author replied us that he do not have time since support is ended

2023-08-27

Recontact Author to confirm versions scope by author

2023-08-27

Author replied us to stop communicating with him

2023-09-21

Request a CVE ID

2023-09-27

Received CVE ID

2023-10-03

Publish this security advisory

**Links**

*   Author product page
*   National Vulnerability Database

**DISCLAIMER:** _The French Association Friends Of Presta (FOP) acts as an intermediary to help hosting this advisory. While we strive to ensure the information and advice provided are accurate, FOP cannot be held liable for any consequences arising from reported vulnerabilities or any subsequent actions taken._

CVE-2023-43983: [CVE-2023-43983] Improper neutralization of SQL parameter in Presto Changeo - Attribute Grid module for PrestaShop

An issue in D-Link Wireless MU-MIMO Gigabit AC1200 Router DIR-846 firmware version 100A53DBR-Retail allows a remote attacker to execute arbitrary code.

CVE-2023-43284

Prixan prixanconnect up to v1.62 was discovered to contain a SQL injection vulnerability via the component CartsGuruCatalogModuleFrontController::importProducts().

**IMPORTANT NOTICE**: DO NOT REPORT VULNERABILITIES SOLELY TO THE AUTHOR OR MARKETPLACE.

We urge you to report any vulnerabilities directly to us. Our mission is to ensure the safety and security of the PrestaShop ecosystem. Unfortunately, many module developers may not always recognize or acknowledge the vulnerabilities in their code, whether due to lack of awareness, or inability to properly evaluate the associated risk, or other reasons.

Given the rise in professional cybercrime networks actively seeking out these vulnerabilities, it's crucial that any potential threats are promptly addressed and the community is informed. The most effective method to do this is by publishing a CVE, like the one provided below.

Should you discover any vulnerabilities, **please report them to us at: report\[@\]security-presta.org**.

Every vulnerability report helps make the community more secure, and we are profoundly grateful for any information shared with us.

In the module “Prixan connect” (prixanconnect) for PrestaShop, an attacker can perform a blind SQL injection before 1.62 without restrictions. Release 1.62 fixed this security issue.

**Summary**

*   **CVE ID**: CVE-2023-40920
*   **Published at**: 2023-10-05
*   **Advisory source**: Friends-Of-Presta.org
*   **Vendor**: PrestaShop
*   **Product**: prixanconnect
*   **Impacted release**: <= 1.61 (1.62 fixed the issue)
*   **Product author**: Prixan
*   **Weakness**: CWE-89
*   **Severity**: critical (9.8)

**Description**

Up to Release 1.63, multiple sensitive SQL calls in class PrixanconnectUpdateProductsModuleFrontController::importProducts() can be executed with a trivial http call and exploited to forge a blind SQL injection throught a json string posted in the body content.

**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**

*   Obtain admin access
*   Remove data from the associated PrestaShop
*   Copy/paste data from sensitive tables to FRONT to expose tokens and unlock admins’s ajax scripts
*   Rewrite SMTP settings to hijack emails

**Patch**

    --- a/prixanconnect/controllers/front/Products.php
    +++ b/prixanconnect/controllers/front/Products.php
    @@ -33,21 +33,21 @@ class PrixanconnectProductsModuleFrontCo
              LEFT JOIN `" . _DB_PREFIX_ . "product_attribute` AS pa ON pa.`id_product_attribute` = pashop.`id_product_attribute`
              LEFT JOIN `" . _DB_PREFIX_ . "product_attribute_combination` AS combi ON combi.`id_product_attribute` = pashop.`id_product_attribute`
              LEFT JOIN `" . _DB_PREFIX_ . "attribute` as attr ON attr.`id_attribute` = combi.`id_attribute`
    -         LEFT JOIN `" . _DB_PREFIX_ . "attribute_lang` as attlang ON attlang.`id_attribute` = attr.`id_attribute` AND attlang.`id_lang` = " . $langID . "
    +         LEFT JOIN `" . _DB_PREFIX_ . "attribute_lang` as attlang ON attlang.`id_attribute` = attr.`id_attribute` AND attlang.`id_lang` = " . (int)$langID . "
              LEFT JOIN `" . _DB_PREFIX_ . "attribute_group_lang`AS grouplang ON grouplang.`id_attribute_group` = attr.`id_attribute_group` AND grouplang.`id_lang` = attlang.`id_lang`
    -         WHERE prshop.`id_shop` = " . $idShop;
    +         WHERE prshop.`id_shop` = " . (int)$idShop;
             if ($only_active === 1) {
                 $query .= " AND prshop.`active` = 1";
             }
             if (!empty($date_from)) {
    -            $query .= " AND prshop.`date_upd` > '$date_from'";
    +            $query .= ' AND prshop.`date_upd` > "'.pSQL($date_from).'"';
             }
     
             if (!empty($product_ids) && count($product_ids) > 0) {
    -            $query .= ' AND prshop.`id_product` IN (' . join(',', $product_ids) . ') ';
    +            $query .= ' AND prshop.`id_product` IN (' . implode(',', array_map('intval', $product_ids)) . ') ';
             }
     
    -        $query .= " ORDER BY prshop.`id_product`  $limit";
    +        $query .= " ORDER BY prshop.`id_product` ". (int) $limit;
     
             return $query;
         }
    
    @@ -177,21 +157,12 @@ INNER JOIN `" . _DB_PREFIX_ . "orders` O
             WHERE pt.name = \"product\" GROUP BY  p.id_object ) view_counter on (view_counter.obj_id=producttable.`id_product`) ";
    
             $mainSqlQuery = "SELECT producttable.id_product, od.sales_count,od.sales,od.purchase_cost FROM 
             `" . _DB_PREFIX_ . "product` AS producttable
                    INNER JOIN  `" . _DB_PREFIX_ . "product_shop` AS prshop  ON producttable.`id_product`= prshop.`id_product`
                     INNER JOIN $sqlSubQuerySalesCount
    -        WHERE prshop.`active` = 1 AND prshop.`id_shop` = " . $idShop;
    -
    -        //   LEFT JOIN $sqlSubQueryViews
    +        WHERE prshop.`active` = 1 AND prshop.`id_shop` = " . (int)$idShop;
     
    -        // $mainSqlQuery = $this->parseDateAndAddToSqlQuery($mainSqlQuery, 'start_date', '>=', false);
    -        // $mainSqlQuery = $this->parseDateAndAddToSqlQuery($mainSqlQuery, 'end_date', '<=', true);
     
             if (Tools::getValue('ids') != null) {
                 $splitted = explode(',', Tools::getValue('ids'));
    
    --- a/prixanconnect/controllers/front/ProductsStats.php
    +++ b/prixanconnect/controllers/front/ProductsStats.php
    @@ -177,66 +161,25 @@ INNER JOIN `" . _DB_PREFIX_ . "orders` O
             WHERE pt.name = \"product\" GROUP BY  p.id_object ) view_counter on (view_counter.obj_id=producttable.`id_product`) ";
             $mainSqlQuery = "SELECT producttable.id_product, od.sales_count,od.sales,od.purchase_cost, view_counter.views FROM 
             `" . _DB_PREFIX_ . "product` AS producttable
                    INNER JOIN  `" . _DB_PREFIX_ . "product_shop` AS prshop  ON producttable.`id_product`= prshop.`id_product`
                     INNER JOIN $sqlSubQuerySalesCount
                    LEFT JOIN $sqlSubQueryViews
    -        WHERE prshop.`active` = 1 AND prshop.`id_shop` = " . $idShop;
    +        WHERE prshop.`active` = 1 AND prshop.`id_shop` = " . (int)$idShop;
     
             if (Tools::getValue('ids') != null) {
                 $splitted = explode(',', Tools::getValue('ids'));
                 if (count($splitted) > 0) {
    -                $mainSqlQuery .= ' AND producttable.id_product IN (' . implode(',', $splitted) . ')';
    +                $mainSqlQuery .= ' AND producttable.id_product IN (' . implode(',', array_map('intval', $splitted)) . ')';
                 }
             }
    
    --- a/prixanconnect/controllers/front/ProductsViews.php
    +++ b/prixanconnect/controllers/front/ProductsViews.php
    @@ -176,7 +160,7 @@ class PrixanconnectProductsViewsModuleFr
             `" . _DB_PREFIX_ . "product` AS producttable
                    INNER JOIN  `" . _DB_PREFIX_ . "product_shop` AS prshop  ON producttable.`id_product`= prshop.`id_product`
                    LEFT JOIN $sqlSubQueryViews
    -        WHERE prshop.`active` = 1 AND prshop.`id_shop` = " . $idShop;
    +        WHERE prshop.`active` = 1 AND prshop.`id_shop` = " . (int)$idShop;
    
    @@ -184,7 +168,7 @@ class PrixanconnectProductsViewsModuleFr
             if (Tools::getValue('ids') != null) {
                 $splitted = explode(',', Tools::getValue('ids'));
                 if (count($splitted) > 0) {
    -                $mainSqlQuery .= ' AND producttable.id_product IN (' . implode(',', $splitted) . ')';
    +                $mainSqlQuery .= ' AND producttable.id_product IN (' . implode(',', array_map('intval', $splitted)) . ')';
                 }
             }
    
    --- a/prixanconnect/controllers/front/UpdateProducts.php
    +++ b/prixanconnect/controllers/front/UpdateProducts.php
    @@ -16,18 +16,20 @@ class PrixanconnectUpdateProductsModuleF
         {
             header('Content-type: application/json');
             // $request->getContent();
    +
             die(Tools::jsonEncode(array('check' => 'you must call this url with POST method')));
    +        
         }
         private function getProductAttributes($product_id)
         {
    -        $query = "SELECT id_product_attribute FROM `" . _DB_PREFIX_ . "product_attribute` WHERE id_product=" . $product_id;
    +        $query = "SELECT id_product_attribute FROM `" . _DB_PREFIX_ . "product_attribute` WHERE id_product=" . (int)$product_id;
     
             $results = Db::getInstance()->executeS($query);
             return $results;
         }
         private function getProductFromAttributeId($product_attribute_id)
         {
    -        $query = "SELECT id_product FROM `" . _DB_PREFIX_ . "product_attribute` WHERE id_product_attribute=" . $product_attribute_id;
    +        $query = "SELECT id_product FROM `" . _DB_PREFIX_ . "product_attribute` WHERE id_product_attribute=" . (int)$product_attribute_id;
     
             $results = Db::getInstance()->executeS($query);
             if ($results && count($results) > 0) {
    
    @@ -102,20 +80,14 @@ class PrixanconnectUpdateProductsModuleF
    
         private function changeProductAttributePrice_mode_impact($id_product, $id_product_attribute, $price, $id_shop)
         {
    -        $query = 'SELECT price FROM  `' . _DB_PREFIX_ . 'product` WHERE id_product=' . $id_product;
    +        $query = 'SELECT price FROM  `' . _DB_PREFIX_ . 'product` WHERE id_product=' . (int)$id_product;
             $price_result =    Db::getInstance()->executeS($query);
     
             if ($price_result == null || count($price_result) == 0) {
    @@ -127,16 +99,11 @@ class PrixanconnectUpdateProductsModuleF
             //only shop
    -        $query = 'UPDATE `' . _DB_PREFIX_ . 'product_attribute_shop` SET price=' . $impact_price . ' WHERE id_product_attribute=' . $id_product_attribute;
    +        $query = 'UPDATE `' . _DB_PREFIX_ . 'product_attribute_shop` SET price=' . (float) $impact_price . ' WHERE id_product_attribute=' . (int)$id_product_attribute;
             if (!empty($id_shop)) {
    -            $query .= ' AND id_shop=' . $id_shop;
    +            $query .= ' AND id_shop=' . (int)$id_shop;
             }
     
     
    @@ -147,18 +114,17 @@ class PrixanconnectUpdateProductsModuleF
             if (empty($id_shop)) {
                 $id_shop = 0;
             }
    -        $query = 'INSERT INTO `' . _DB_PREFIX_ . 'specific_price` (id_product,id_product_attribute,price,`from`,`to`,id_shop) VALUES(' . (int) $id_product . ',' . $id_product_attribute . ',' . $price . ',' . "'0000-00-00 00:00:00'" . ',' . "'0000-00-00 00:00:00'" . ',' .  $id_shop . ')';
    +        $query = 'INSERT INTO `' . _DB_PREFIX_ . 'specific_price` (id_product,id_product_attribute,price,`from`,`to`,id_shop) VALUES(' . (int) $id_product . ',' . (int) $id_product_attribute . ',' . (float) $price . ',' . "'0000-00-00 00:00:00'" . ',' . "'0000-00-00 00:00:00'" . ',' .  (int) $id_shop . ')';
             return  Db::getInstance()->execute($query);
     
    -        // $query = "UPDATE `" . _DB_PREFIX_ . "specific_price` SET `from`='1980-01-01 00:00:00', `to`='2100-01-01 00:00:00' WHERE `id_specific_price`=" . $newSpecId;
    -        // return   Db::getInstance()->executeS($query);
    +
         }
         private function deleteSpecificPriceForAttribute($id_product, $id_product_attribute, $id_shop)
         {
             if (empty($id_shop)) {
                 $id_shop = 0;
             }
    -        $query = 'DELETE FROM `' . _DB_PREFIX_ . 'specific_price` WHERE `id_product` = ' . (int) $id_product . ' AND `id_product_attribute` = ' . $id_product_attribute . ' AND id_shop=' . $id_shop;
    +        $query = 'DELETE FROM `' . _DB_PREFIX_ . 'specific_price` WHERE `id_product` = ' . (int) $id_product . ' AND `id_product_attribute` = ' . (int) $id_product_attribute . ' AND id_shop=' . (int)$id_shop;
             Db::getInstance()->execute($query);
         }
         private function updateProductPriceWithCleanSpecific($id, $prix_base, $prix_promo, $idShop)
    @@ -195,15 +161,21 @@ class PrixanconnectUpdateProductsModuleF
         {
             header('Content-type: application/json');
             $returned = array('success' => false, 'products' => array(), 'error' => null);
    +        
             try {
     
                 $idShop = Tools::getValue('id_shop');
    
                 if (!empty($idShop)) {
                     $idShop = (int)  $idShop;
                 }
    +            if (strtoupper(trim($_SERVER['REQUEST_METHOD'])) != 'POST'){
    +                throw new Exception('you must call this url with POST method');
    +            }
    +            $cle_module = Configuration::get('PRIXANCONNECT_CLE');
    +            if (Tools::getValue('key') == false || Tools::getValue('key') != $cle_module) {
    +                throw new Exception('erreur d\'autorisation');
    +            }
     
                 // $entityBody = stream_get_contents(STDIN);
                 $entityBody = file_get_contents('php://input');
    
    @@ -298,10 +264,10 @@ class PrixanconnectUpdateProductsModuleF
                                             if (!is_numeric($prix_base)) {
                                                 throw new Exception('prix_base is not correct');
                                             }
    -                                        $query_result =  Db::getInstance()->executeS('update `' . _DB_PREFIX_ . 'pm_advancedpack` SET fixed_price=' . $prix_base  . ' WHERE id_pack=' . $id);
    +                                        $query_result =  Db::getInstance()->executeS('update `' . _DB_PREFIX_ . 'pm_advancedpack` SET fixed_price=' . (float)$prix_base  . ' WHERE id_pack=' . (int)$id);
                                             $returned['products'][] = array('id' => $id, 'success' => $query_result);
                                         } else {
    -                                        $query_result =  Db::getInstance()->executeS('update `' . _DB_PREFIX_ . 'pm_advancedpack` SET fixed_price=NULL WHERE id_pack=' . $id);
    +                                        $query_result =  Db::getInstance()->executeS('update `' . _DB_PREFIX_ . 'pm_advancedpack` SET fixed_price=NULL WHERE id_pack=' . (int)$id);
                                             $returned['products'][] = array('id' => $id, 'success' => $query_result);
                                         }
                                     } else {
    

**Other recommandations**

*   It’s recommended to upgrade to the latest version of the module **prixanconnect**.
*   Upgrade PrestaShop to the latest version to disable multiquery executions (separated by “;”) - be warned that this functionality **WILL NOT** protect your SHOP against injection SQL which uses the UNION clause to steal data.
*   Change the default database prefix ps_ with a new longer, arbitrary prefix. Nevertheless, be warned that this is useless against blackhats with DBA senior skills 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 this set of rules.

**Timeline**

Date

Action

2023-03-05

Vulnerability discovered during a code reviews by 202 ecommerce

2023-03-07

Contact the author

2023-04-05

The author confirm the vulnerability without possibility to verify the patch

2023-05-29

Retrieve the patched release and ask to the author to fix all sensitive SQL calls

2023-06-15

Retry to contact Prixan team

2023-08-15

Request a CVE ID from Mitre.org

2023-08-25

Recieved the CVE ID

2023-09-25

Inform the author about the scheduled publication of the CVE. Propose 30 days of delay before disclose.

2023-10-05

Publication of this security advisory

**Links**

*   Product page
*   National Vulnerability Database

**DISCLAIMER:** _The French Association Friends Of Presta (FOP) acts as an intermediary to help hosting this advisory. While we strive to ensure the information and advice provided are accurate, FOP cannot be held liable for any consequences arising from reported vulnerabilities or any subsequent actions taken._

CVE-2023-40920: [CVE-2023-40920] Improper neutralization of an SQL parameter in prixanconnect module for PrestaShop

Presto Changeo testsitecreator up to 1.1.1 was discovered to contain a deserialization vulnerability via the component delete_excluded_folder.php.

**IMPORTANT NOTICE**: DO NOT REPORT VULNERABILITIES SOLELY TO THE AUTHOR OR MARKETPLACE.

We urge you to report any vulnerabilities directly to us. Our mission is to ensure the safety and security of the PrestaShop ecosystem. Unfortunately, many module developers may not always recognize or acknowledge the vulnerabilities in their code, whether due to lack of awareness, or inability to properly evaluate the associated risk, or other reasons.

Given the rise in professional cybercrime networks actively seeking out these vulnerabilities, it's crucial that any potential threats are promptly addressed and the community is informed. The most effective method to do this is by publishing a CVE, like the one provided below.

Should you discover any vulnerabilities, **please report them to us at: report\[@\]security-presta.org**.

Every vulnerability report helps make the community more secure, and we are profoundly grateful for any information shared with us.

In the module “Test Site Creator” (testsitecreator) from Presto Changeo for PrestaShop, a guest can execute a remote code via an untrusted data deserialized.

**Summary**

*   **CVE ID**: CVE-2023-43981
*   **Published at**: 2023-10-03
*   **Platform**: PrestaShop
*   **Product**: testsitecreator
*   **Impacted release**: <= 1.1.1 (WARNING : see WARNING below)
*   **Product author**: Presto Changeo
*   **Weakness**: CWE-502
*   **Severity**: critical (10)

**Description**

A deserialization of untrusted data in scripts delete\_excluded\_folder.php and verify\_excluded\_folder.php can be used with a trivial http call and exploited to execute a remote code.

**WARNING** : Author discontinue support of its module so you should no longer continue to use them and do not have time to confirm us the scope of impacted versions so it could impact newer versions than 1.1.1.

**CVSS base metrics**

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

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

**Possible malicious usage**

*   Obtain admin access
*   Steal/Remove data from the associated PrestaShop

**Patch from 1.1.1**

    --- 1.1.1/modules/testsitecreator/lib/verify_excluded_folder.php
    +++ XXXXX/modules/testsitecreator/lib/verify_excluded_folder.php
    ...
    -	$tsc_excluded_folders = unserialize(Tools::getValue('tsc_excluded_folders'));
    +	$tsc_excluded_folders = unserialize(Tools::getValue('tsc_excluded_folders'), ['allowed_classes' => false]);
    

    --- 1.1.1/modules/testsitecreator/lib/delete_excluded_folder.php
    +++ XXXXX/modules/testsitecreator/lib/delete_excluded_folder.php
    ...
    -	$tsc_excluded_folders = unserialize(Tools::getValue('tsc_excluded_folders'));
    +	$tsc_excluded_folders = unserialize(Tools::getValue('tsc_excluded_folders'), ['allowed_classes' => false]);
    

**Other recommendations**

*   Since author discontinue support on its modules, it is recommended to delete the module.
*   Activate OWASP 933’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 this set of rules.

**Timeline**

Date

Action

2023-08-10

Issue discovered during a code review by TouchWeb.fr

2023-08-10

Contact Author to confirm versions scope by author

2023-08-27

Recontact Author to confirm versions scope by author

2023-08-27

Author replied us to stop communicating with him

2023-09-21

Request a CVE ID

2023-09-27

Received CVE ID

2023-10-03

Publish this security advisory

**Links**

*   Author product page
*   National Vulnerability Database

**DISCLAIMER:** _The French Association Friends Of Presta (FOP) acts as an intermediary to help hosting this advisory. While we strive to ensure the information and advice provided are accurate, FOP cannot be held liable for any consequences arising from reported vulnerabilities or any subsequent actions taken._

CVE-2023-43981: [CVE-2023-43981] Deserialization of Untrusted Data in Presto Changeo - Test Site Creator module for PrestaShop

A NULL pointer dereference flaw was found in the Linux kernel ipv4 stack. The socket buffer (skb) was assumed to be associated with a device before calling __ip_options_compile, which is not always the case if the skb is re-routed by ipvs. This issue may allow a local user with CAP_NET_ADMIN privileges to crash the system.

**Red Hat Product Security Center**

Engage with our Red Hat Product Security team, access security updates, and ensure your environments are not exposed to any known security vulnerabilities.

Product Security Center

CVE-2023-42754: cve-details

LibTIFF is vulnerable to an integer overflow. This flaw allows remote attackers to cause a denial of service (application crash) or possibly execute an arbitrary code via a crafted tiff image, which triggers a heap-based buffer overflow.

CVE-2023-40745: cve-details

A vulnerability was found in libtiff due to multiple potential integer overflows in raw2tiff.c. This flaw allows remote attackers to cause a denial of service or possibly execute an arbitrary code via a crafted tiff image, which triggers a heap-based buffer overflow.

CVE-2023-41175: cve-details

A flaw was found in the IPv4 Resource Reservation Protocol (RSVP) classifier in the Linux kernel. The xprt pointer may go beyond the linear part of the skb, leading to an out-of-bounds read in the `rsvp_classify` function. This issue may allow a local user to crash the system and cause a denial of service.

CVE-2023-42755: cve-details

Milesight UR5X, UR32L, UR32, UR35, UR41 before v35.3.0.7 was discovered to contain a cross-site scripting (XSS) vulnerability via the admin panel.

**Reflected Cross-Site Scripting (XSS) and Absent HttpOnly Flag in Ursalink Industrial Cellular Router Admin Panel Leads to Account Takeover****Vulnerability Details**

Cross-Site Scripting (XSS) and Absent HttpOnly Flag vulnerabilities in Ursalink Industrial Cellular Router admin panel could allow remote attackers to execute arbitrary scripts and hijack user sessions, potentially leading to account takeover.

The admin panel does not properly validate and sanitize user inputs, allowing malicious scripts to be injected into the page's content. The "td" session cookie lacks the HttpOnly flag (and also Secure Flag), enabling client-side scripts to access it, leading to session hijacking and unauthorized access. Attackers can steal sensitive information, impersonate users, or perform unauthorized actions.

*   **Affected Products**: UR5X, UR32L, UR32, UR35, UR41 and there might be other Industrial Cellular Routers could also be vulnerable.
*   **Affected Firmware**: All including Latest v35.3.0.7
*   **Vulnerability Type (CWEs)**:
    1.  Improper Neutralization of Input During Web Page Generation \['Cross-site Scripting'\] (CWE-79)
    2.  Sensitive Cookie Without 'HttpOnly' Flag (CWE-1004)
    3.  Sensitive Cookie in HTTPS Session Without 'Secure' Flag (CWE-614)
*   **Severity**: Medium (CVSS 4.5/10), Vector String - CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
*   **Vendor of the product**: Milesight (Formerly Xiamen Ursalink Technology Co., Ltd.)
*   **Credits/Reported By**: Bipin Jitiya (@win3zz)

**Proof of Concept (PoC)**

*   When any input provided after "/cgi-bin/" in the URL is echoed back without proper output encoding.
*   Access the Ursalink Industrial Cellular Router admin panel, and modify the URL to inject a malicious script/payload, e.g.: /cgi-bin/any?param=<script>alert(document.cookie)</script>.
*   Observe the executed payload in the browser, confirming the presence of the XSS vulnerability.

*   Also, observe the login response in the Burp Repeater tool showing the "Set-Cookie" header without the **HttpOnly** and **Secure** flags.

**Disclosure Timeline**

*   **August 22, 2023**: Initial vendor notification regarding the vulnerability.
*   **August 31, 2023**: Received response from Milesight, expressing appreciation for the report and agreeing that the identified issues can be improved in future updates.
*   **September 12, 2023**: Requested for CVE-ID
*   **September 26, 2023**: CVE-2023-43260 assigned
*   **September 28, 2023**: Notified the company about public disclosure
*   **October 5, 2023**: Public disclosure

Source

CVE