Skip links

[CVE-2021-42064] SQL Injection vulnerability in SAP Commerce, SAP security note 3114134



If SAP Commerce is configured to use an Oracle database and if a query is created using the flexible search java api with a parametrized “in” clause SAP Commerce allows attacker to execute crafted database queries, exposing backend database. The vulnerability is present if the parametrized “in” clause accepts more than 1000 values.

The problem can affect any kind of extension using the flexible search api with an “in” clause with partially untrusted input and potentially some internal components of the platform when using an Oracle database.

Other Terms

Injection attack, blind SQL injection, database vulnerabilities, CVE-2021-42064

Reason and Prerequisites

Any SAP Commerce installation using Oracle database is impacted.


SAP Commerce addresses this vulnerability by properly escaping any value passed to parametrized “in” clause when handling flexible search queries having more than 1000 values used in this clause.

The following patch releases address this vulnerability:

The Software Downloads of these or later patches are available in the SAP Support Portal. For information about installing patches, see About Patch Releases.


Available fix and Supported packages


Affected component





Detailed vulnerability information added to RedRays Security Platform. Contact [email protected] for details.



Injection attack, blind SQL injection, database vulnerabilities, CVE-2021-42064

How to detect over 4100 vulnerabilities in SAP Systems?

More to explorer

Initiating SAP Penetration Testing

►   Pentest, short for penetration testing, refers to a set of processes that simulate an attacker’s actions to identify security vulnerabilities. Companies

SAP Security Patch Day RedRays

May 2024 SAP Security Patch Day

Vulnerability: Multiple vulnerabilities in SAP CX Commerce SAP Component: CEC-SCC-PLA-PL CVE ID: CVE-2019-17495 CVSS Score: 9.8 CVSS Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Category: Program error