Skip to content
OpenAdvisories

Weakness (CWE)

CWE-89: Improper Neutralization of Special Elements used in an SQL Command

Base

The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

How to prevent it (8 mitigations)

  1. Architecture and Design

    Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].

    For example, consider using persistence layers such as Hibernate or Enterprise Java Beans, which can provide significant protection against SQL injection if used properly.

  2. Architecture and Design

    If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.

    Process SQL queries using prepared statements, parameterized queries, or stored procedures. These features should accept parameters or variables and support strong typing. Do not dynamically construct and execute query strings within these features using "exec" or similar functionality, since this may re-introduce the possibility of SQL injection. [REF-867]

  3. Architecture and Design, Operation

    Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.

    Specifically, follow the principle of least privilege when creating user accounts to a SQL database. The database users should only have the minimum privileges necessary to use their account. If the requirements of the system indicate that a user can read and modify their own data, then limit their privileges so they cannot read/write others' data. Use the strictest permissions possible on all database objects, such as execute-only for stored procedures.

  4. Architecture and Design

    For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.

  5. Implementation

    While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).

    Instead of building a new implementation, such features may be available in the database or programming language. For example, the Oracle DBMS_ASSERT package can check or enforce that parameters have certain properties that make them less vulnerable to SQL injection. For MySQL, the mysql_real_escape_string() API function is available in both C and PHP.

  6. Implementation

    Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.

    When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."

    Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.

    When constructing SQL query strings, use stringent allowlists that limit the character set based on the expected value of the parameter in the request. This will indirectly limit the scope of an attack, but this technique is less important than proper output encoding and escaping.

    Note that proper output encoding, escaping, and quoting is the most effective solution for preventing SQL injection, although input validation may provide some defense-in-depth. This is because it effectively limits what will appear in output. Input validation will not always prevent SQL injection, especially if you are required to support free-form text fields that could contain arbitrary characters. For example, the name "O'Reilly" would likely pass the validation step, since it is a common last name in the English language. However, it cannot be directly inserted into the database because it contains the "'" apostrophe character, which would need to be escaped or otherwise handled. In this case, stripping the apostrophe might reduce the risk of SQL injection, but it would produce incorrect behavior because the wrong name would be recorded.

    When feasible, it may be safest to disallow meta-characters entirely, instead of escaping them. This will provide some defense in depth. After the data is entered into the database, later processes may neglect to escape meta-characters before use, and you may not have control over those processes.

  7. Architecture and Design

    When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.

  8. Implementation

    Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success.

    If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files.

    Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.

    In the context of SQL Injection, error messages revealing the structure of a SQL query can help attackers tailor successful attack strings.

Source: MITRE CWE-89

All Critical High Medium Low Exploited only Public exploit

114 results · Clear filters · Feed

  • Medium 6.3
    CVE-2025-7558 Public exploit

    code-projects Voting System positions_add.php sql injection

    A vulnerability was found in code-projects Voting System 1.0 and classified as critical. Affected by this issue is some unknown functionality of the file /admin/positions_add.php. The manipulation of the argument description leads to sql injection. The attack…

    code-projects Voting System
  • Medium 5.4
    CVE-2025-45809 Public exploit

    SQL Injection vulnerability in BerriAI LiteLLM before 1.81.0 allows attackers to execute arbitrary commands via the key…

  • Medium 4.7
    CVE-2025-6867 Public exploit

    SourceCodester Simple Company Website manage.php sql injection

    A vulnerability was found in SourceCodester Simple Company Website 1.0 and classified as critical. This issue affects some unknown processing of the file /admin/services/manage.php. The manipulation of the argument ID leads to sql injection. The attack may be…

    SourceCodester Simple Company Website
  • Medium 6.3
    CVE-2025-6860 Public exploit

    SourceCodester Best Salon Management System staff_commision.php sql injection

    A vulnerability was found in SourceCodester Best Salon Management System 1.0. It has been declared as critical. This vulnerability affects unknown code of the file /panel/staff_commision.php. The manipulation of the argument fromdate/todate leads to sql injec…

    SourceCodester Best Salon Management System
  • Medium 6.5
    CVE-2025-29529 Public exploit

    ITC Systems Multiplan/Matrix OneCard platform v3.7.4.1002 was discovered to contain a SQL injection vulnerability via t…

  • Medium 6.3
    CVE-2025-3243 Public exploit

    code-projects Patient Record Management System dental_form.php sql injection

    A vulnerability was found in code-projects Patient Record Management System 1.0 and classified as critical. This issue affects some unknown processing of the file /dental_form.php. The manipulation of the argument itr_no/dental_no leads to sql injection. The …

    code-projects Patient Record Management System
  • Medium 6.5
    CVE-2021-37787 Public exploit

    The unprivileged administrative interface in ABO.CMS version 5.8 through v.5.9.3 is affected by a SQL Injection vulnera…

  • Medium 6.3
    CVE-2025-2126 Public exploit EPSS 11%

    JoomlaUX JUX Real Estate GET Parameter realties sql injection

    A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the file /extensions/realestate/index.php/properties/list/list-with-sidebar/realties of the component GET Parameter…

    JoomlaUX JUX Real Estate
  • Medium 4.7
    CVE-2024-11956 Public exploit

    Pimcore customer-data-framework list sql injection

    A vulnerability, which was classified as critical, has been found in Pimcore customer-data-framework up to 4.2.0. Affected by this issue is some unknown functionality of the file /admin/customermanagementframework/customers/list. The manipulation of the argum…

    pimcore customer-data-framework pimcore/customer-management-framework-bundle Packagist
  • Medium 6.3
    CVE-2024-54761 Public exploit

    BigAnt Office Messenger 5.6.06 is vulnerable to SQL Injection via the 'dev_code' parameter.

  • Medium 6.9
    CVE-2024-56801 Public exploit

    Tasklists has Blind SQL Injection in /ajax/reorder.php

    Tasklists provides plugin tasklists for GLPI. Versions prior to 2.0.4 have a blind SQL injection vulnerability. Version 2.0.4 contains a patch for the vulnerability.

    InfotelGLPI tasklists
  • Medium 6.5
    CVE-2024-50970 Public exploit

    A SQL injection vulnerability in orderview1.php of Itsourcecode Online Furniture Shopping Project 1.0 allows remote att…

  • Medium 6.5
    CVE-2024-50971 Public exploit

    A SQL injection vulnerability in print.php of Itsourcecode Construction Management System 1.0 allows remote attackers t…

  • Medium 6.5
    CVE-2024-50972 Public exploit

    A SQL injection vulnerability in printtool.php of Itsourcecode Construction Management System 1.0 allows remote attacke…

  • Medium 4.3
    CVE-2024-40443 Public exploit

    SQL Injection vulnerability in Simple Laboratory Management System using PHP and MySQL v.1.0 allows a remote attacker t…

  • Medium 6.5
    CVE-2024-51030 Public exploit

    A SQL injection vulnerability in manage_client.php and view_cab.php of Sourcecodester Cab Management System 1.0 allows …

  • Medium 4.9
    CVE-2024-8309 Public exploit EPSS 14%

    SQL Injection in langchain-ai/langchain

    A vulnerability in the GraphCypherQAChain class of langchain-ai/langchain version 0.2.5 allows for SQL injection through prompt injection. This vulnerability can lead to unauthorized data manipulation, data exfiltration, denial of service (DoS) by deleting al…

    langchain-ai langchain-ai/langchain langchain langchain-community PyPI
  • Medium 4.7
    CVE-2024-10355 Public exploit

    SourceCodester Petrol Pump Management Software invoice.php sql injection

    A vulnerability, which was classified as critical, has been found in SourceCodester Petrol Pump Management Software 1.0. Affected by this issue is some unknown functionality of the file /admin/invoice.php. The manipulation of the argument id leads to sql inje…

    SourceCodester Petrol Pump Management Software
  • Medium 4.7
    CVE-2024-10354 Public exploit

    SourceCodester Petrol Pump Management Software print.php sql injection

    A vulnerability classified as critical was found in SourceCodester Petrol Pump Management Software 1.0. Affected by this vulnerability is an unknown functionality of the file /admin/print.php. The manipulation of the argument id leads to sql injection. The at…

    SourceCodester Petrol Pump Management Software
  • Medium 6.3
    CVE-2024-10140 Public exploit

    code-projects Pharmacy Management System manage_supplier.php sql injection

    A vulnerability, which was classified as critical, has been found in code-projects Pharmacy Management System 1.0. Affected by this issue is some unknown functionality of the file /manage_supplier.php. The manipulation of the argument id leads to sql injectio…

    code-projects Pharmacy Management System
  • Medium 6.3
    CVE-2024-7801 Public exploit

    SQL injection in get_chart_data in TimeProvider 4100

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Microchip TimeProvider 4100 (Data plot modules) allows SQL Injection.This issue affects TimeProvider 4100: from 1.0 before 2.4.7.

    Microchip TimeProvider 4100
  • Medium 5.5
    CVE-2024-8945 Public exploit EPSS 16%

    CodeCanyon RISE Ultimate Project Manager save sql injection

    A vulnerability has been found in CodeCanyon RISE Ultimate Project Manager 3.7.0 and classified as critical. This vulnerability affects unknown code of the file /index.php/dashboard/save. The manipulation of the argument id leads to sql injection. The attack …

    CodeCanyon RISE Ultimate Project Manager
  • Medium 6.0
    CVE-2024-37791 Public exploit

    DuxCMS3 v3.1.3 was discovered to contain a SQL injection vulnerability via the keyword parameter at /article/Content/in…

  • Medium 6.3
    CVE-2024-6039 Public exploit

    Feng Office Workspaces sql injection

    A vulnerability, which was classified as critical, was found in Feng Office 3.11.1.2. Affected is an unknown function of the component Workspaces. The manipulation of the argument dim leads to sql injection. It is possible to launch the attack remotely. The e…

  • Medium 5.4
    CVE-2024-36837 Public exploit

    SQL Injection vulnerability in CRMEB v.5.2.2 allows a remote attacker to obtain sensitive information via the getProduc…

  • Medium 5.4
    CVE-2024-35468 Public exploit

    A SQL injection vulnerability in /hrm/index.php in SourceCodester Human Resource Management System 1.0 allows attackers…

  • Medium 4.7
    CVE-2024-35511 Public exploit

    phpgurukul Men Salon Management System v2.0 is vulnerable to SQL Injection via the "username" parameter of /msms/admin/…

  • Medium 6.3
    CVE-2024-5356 Public exploit

    anji-plus AJ-Report testTransform;swagger-ui sql injection

    A vulnerability, which was classified as critical, was found in anji-plus AJ-Report up to 1.4.1. Affected is an unknown function of the file /dataSet/testTransform;swagger-ui. The manipulation of the argument dynSentence leads to sql injection. It is possible…

    anji-plus AJ-Report
  • Medium 6.3
    CVE-2024-36039 Public exploit

    PyMySQL SQL Injection vulnerability

    PyMySQL through 1.1.0 allows SQL injection if used with untrusted JSON input because keys are not escaped by escape_dict.

    pymysql python-pymysql python-pymysql Debian Ubuntu PyPI
  • Medium 5.9
    CVE-2024-34222 Public exploit

    Sourcecodester Human Resource Management System 1.0 is vulnerable to SQL Injection via the searccountry parameter.

  • Medium 4.3
    CVE-2024-32369 Public exploit

    SQL Injection vulnerability in HSC Cybersecurity HC Mailinspector 5.2.17-3 through 5.2.18 allows a remote attacker to o…

  • Medium 5.5
    CVE-2024-34472 Public exploit

    An issue was discovered in HSC Mailinspector 5.2.17-3 through v.5.2.18. An authenticated blind SQL injection vulnerabil…

  • Medium 5.3
    CVE-2023-45503 Public exploit

    SQL Injection vulnerability in Macrob7 Macs CMS 1.1.4f, allows remote attackers to execute arbitrary code, cause a deni…

  • Medium 6.3
    CVE-2024-3690 Public exploit

    PHPGurukul Small CRM Change Password sql injection

    A vulnerability classified as critical was found in PHPGurukul Small CRM 3.0. Affected by this vulnerability is an unknown functionality of the component Change Password Handler. The manipulation leads to sql injection. The attack can be launched remotely. Th…

    PHPGurukul Small CRM
  • Medium 6.1
    CVE-2024-2387 Public exploit

    Advanced Form Integration – Connect WooCommerce and Contact Form 7 to Google Sheets and other platforms <= 1.82.0 - SQL Injection to Reflected Cross-Site Scripting via integration_id

    The Advanced Form Integration – Connect WooCommerce and Contact Form 7 to Google Sheets and other platforms plugin for WordPress is vulnerable to SQL Injection via the ‘integration_id’ parameter in all versions up to, and including, 1.82.0 due to insufficient…

    nasirahmed AFI – The Easiest Integration Plugin Web / CMS
  • Medium 6.5
    CVE-2024-25227 Public exploit

    SQL Injection vulnerability in ABO.CMS version 5.8, allows remote attackers to execute arbitrary code, cause a denial o…

  • Medium 4.3
    CVE-2023-49969 Public exploit

    Customer Support System v1 was discovered to contain a SQL injection vulnerability via the id parameter at /customer_su…

  • Medium 6.3
    CVE-2024-2074 Public exploit

    Mini-Tmall 1 sql injection

    A vulnerability was found in Mini-Tmall up to 20231017 and classified as critical. This issue affects some unknown processing of the file ?r=tmall/admin/user/1/1. The manipulation of the argument orderBy leads to sql injection. The attack may be initiated rem…

  • Medium 4.9
    CVE-2023-49544 Public exploit

    A local file inclusion (LFI) in Customer Support System v1 allows attackers to include internal PHP files and gain unau…

  • Medium 5.9
    CVE-2023-44088 Public exploit

    SQL Injection in Visual Console

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Pandora FMS on all allows SQL Injection. Arbitrary SQL queries were allowed to be executed using any account with low privileges. This issue affects Pandora …

    Pandora FMS Pandora FMS