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

650 results · Clear filters · Feed

  • Critical 9.3
    CVE-2026-39492 Public exploit

    WordPress WP Maps plugin <= 4.9.1 - SQL Injection vulnerability

    Unauthenticated SQL Injection in WP Maps <= 4.9.1 versions.

    Flipper Code – WordPress Development Company WP Maps
  • Critical 9.8
    CVE-2026-38812 Public exploit

    RuoYi v4.8.2 is vulnerable to SQL Injection via the /tool/gen/createTable endpoint. The issue affects the code generati…

  • High 8.8
    CVE-2026-36670 Public exploit

    A Time-Based Blind SQL Injection vulnerability in the alias_management module of OpenSIPS Control Panel (opensips-cp) p…

  • High 7.5
    CVE-2026-9848 Public exploit

    WP Ticket <= 6.0.4 - Unauthenticated SQL Injection via WordPress Search 's' Parameter

    The WP Ticket plugin for WordPress is vulnerable to SQL Injection via the WordPress search query parameter (`s`) in versions up to, and including, 6.0.4 The plugin hooks WordPress's `posts_request` filter with `wp_ticket_com_posts_request()`, which calls `emd…

    emarket-design Customer Support Ticket System & Helpdesk Web / CMS
  • Critical 9.3
    CVE-2026-42647 Public exploit

    WordPress JoomSport plugin <= 5.7.7 - SQL Injection vulnerability

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Beardev JoomSport allows Blind SQL Injection. This issue affects JoomSport: from n/a through 5.7.7.

    Beardev JoomSport
  • High 8.6
    CVE-2026-3326 Public exploit

    XStore < 9.7.3 - Unauthenticated SQLi

    The Xstore WordPress theme before 9.7.3 does not properly sanitise and escape a parameter before using it in a SQL statement via an AJAX action available to unauthenticated users, leading to a SQL injection

    Web / CMS
  • High 7.8
    CVE-2026-0075 Public exploit

    In multiple functions, there is a possible way to access the contacts database due to a SQL injection. This could lead …

    Google Android Android
  • High 7.3
    CVE-2026-10290 Public exploit

    code-projects Hotel and Tourism Reservation System GET Parameter tour.php sql injection

    A weakness has been identified in code-projects Hotel and Tourism Reservation System 1.0. The affected element is an unknown function of the file tour.php of the component GET Parameter Handler. Executing a manipulation of the argument tour can lead to sql in…

    code-projects Hotel and Tourism Reservation System
  • Medium 6.3
    CVE-2026-10170 Public exploit

    code-projects Visitor Management System phone_0.php sql injection

    A flaw has been found in code-projects Visitor Management System 1.0. Affected by this issue is some unknown functionality of the file /vms/php/phone_0.php. This manipulation of the argument phone causes sql injection. The attack may be initiated remotely. Th…

    code-projects Visitor Management System
  • High 7.3
    CVE-2026-10110 Public exploit

    code-projects Student Details Management System index.php sql injection

    A vulnerability was detected in code-projects Student Details Management System 1.0. This affects an unknown function of the file /index.php. Performing a manipulation of the argument roll results in sql injection. The attack is possible to be carried out rem…

    code-projects Student Details Management System
  • Critical 10.0
    CVE-2026-8054 Public exploit

    Unauthenticated SQL Injection in dotCMS Publish Audit API

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in the Publish Audit API endpoints (/api/auditPublishing/get and /api/auditPublishing/getAll) in dotCMS Core 25.11.04-1 through 26.04.28-02 allows remote unauthenticated atta…

    dotCMS dotCMS Core
  • High 8.5
    CVE-2026-44706 Public exploit

    Chatwoot: SQL Injection in Conversation/Contact Filter API via Custom Attribute Values

    Chatwoot is a customer engagement suite. From 2.2.0 to before 4.11.2, a SQL injection vulnerability exists in the conversation and contact filter APIs. When filtering by a custom attribute of type date or number using the is_greater_than or is_less_than opera…

    chatwoot chatwoot
  • High 7.6
    CVE-2026-44680 Public exploit

    MikroORM: SQL injection via runtime-controlled identifiers and JSON-path keys

    MikroORM is a TypeScript ORM for Node.js based on Data Mapper, Unit of Work and Identity Map patterns. Prior to @mikro-orm/knex 6.6.14 and @mikro-orm/sql 7.0.14, MikroORM's identifier-quoting helper (Platform.quoteIdentifier and the postgres/mssql overrides) …

    mikro-orm mikro-orm sql knex npm
  • High 8.1
    CVE-2026-48842 Public exploit

    Roundcube Webmail 1.6.x before 1.6.16 and 1.7.x before 1.7.1 has Pre-authentication SQL injection in the virtuser_query…

    Roundcube Webmail roundcube roundcube Debian Ubuntu
  • Critical 9.8
    CVE-2026-9082 Exploited Public exploit EPSS 89%

    Drupal core - Highly critical - SQL injection - SA-CORE-2026-004

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Drupal Drupal core allows SQL Injection. This issue affects Drupal core: from 8.9.0 before 10.4.10, from 10.5.0 before 10.5.10, from 10.6.0 before 10.6.9, fr…

    Drupal Drupal core drupal/core Web / CMS Packagist
    KEV May 22, 2026
  • High 8.2
    CVE-2026-8726 Public exploit

    SQL Injection in extension "News system" (news)

    The extension fails to properly sanitize user input before using it in a database query. As a result, an unauthenticated attacker can inject arbitrary SQL through a URL parameter on pages using the "Date Menu of news articles" plugin. Exploitation requires th…

    TYPO3 Extension "News system" georgringer/news Packagist
  • High 8.6
    CVE-2026-6379 Public exploit

    WP Photo Album Plus < 9.1.11.001 - Unauthenticated SQL Injection via 'wppa-supersearch' Parameter

    The WP Photo Album Plus WordPress plugin before 9.1.11.001 does not properly sanitize and escape a parameter before using it in a SQL query, allowing unauthenticated users to perform SQL injection attacks.

    Web / CMS
  • Critical 9.3
    CVE-2026-22599 Public exploit

    Strapi Vulnerable to SQL Injection in Content Type Builder

    Strapi is an open source headless content management system. In versions on the 4.x branch prior to 4.26.1 and on the 5.x branch prior to 5.33.2, a database-query injection vulnerability existed in the Strapi Content-Type Builder write API. An authenticated a…

    strapi strapi @strapi/content-type-builder @strapi/content-type-builder npm
  • High 8.3
    CVE-2026-42031 Public exploit

    CKAN: Unauthenticated SQL Injection and Authorization Bypass in `datastore_search_sql`

    CKAN is an open-source DMS (data management system) for powering data hubs and data portals. Prior to 2.10.10 and 2.11.5, a vulnerability in datastore_search_sql allowed attackers to inject SQL in order to gain access to private resources and PostgreSQL syste…

    ckan ckan ckan PyPI
  • Critical 9.3
    CVE-2026-42208 Exploited Public exploit EPSS 89%

    LiteLLM: SQL injection in Proxy API key verification

    LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. From version 1.81.16 to before version 1.83.7, a database query used during proxy API key checks mixed the caller-supplied key value into the query text instead of passing i…

    BerriAI litellm litellm PyPI
    KEV May 8, 2026
  • Medium 6.3
    CVE-2024-33722 Public exploit

    SOPlanning 1.52.00 is vulnerable to SQL Injection by an authenticated user via projets.php with statut[].

  • High 8.3
    CVE-2026-41490 Public exploit

    Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations

    Dagster is an orchestration platform for the development, production, and observation of data assets. Prior to Dagster Core version 1.13.1 and prior to Dagster libraries version 0.29.1, the DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed S…

    dagster-io dagster dagster dagster-duckdb PyPI
  • High 7.5
    CVE-2026-3359 Public exploit

    Form Maker by 10Web – Mobile-Friendly Drag & Drop Contact Form Builder <= 1.15.42 - Unauthenticated SQL Injection via 'inputs'

    The Form Maker by 10Web – Mobile-Friendly Drag & Drop Contact Form Builder plugin for WordPress is vulnerable to SQL Injection via the 'inputs' parameter in versions up to, and including, 1.15.42 due to insufficient escaping on the user supplied parameter and…

    10web Form Maker by 10Web – Mobile-Friendly Drag & Drop Contact Form Builder Web / CMS
  • High 7.5
    CVE-2026-3456 Public exploit

    GeekyBot — Generate AI Content Without Prompt, Chatbot and Lead Generation <= 1.2.0 - Unauthenticated SQL Injection via 'attributekey'

    The GeekyBot — Generate AI Content Without Prompt, Chatbot and Lead Generation plugin for WordPress is vulnerable to SQL Injection via the 'attributekey' parameter in versions up to, and including, 1.2.0 due to insufficient escaping on the user supplied param…

    ahmadgb GeekyBot — AI Copilot, Chatbot, WooCommerce Lead Gen & Zero-Prompt Content Web / CMS
  • Medium 6.3
    CVE-2026-7731 Public exploit

    code-projects BloodBank Managing System get_state.php sql injection

    A security vulnerability has been detected in code-projects BloodBank Managing System 1.0. The affected element is an unknown function of the file get_state.php. The manipulation of the argument G_STATE_ID leads to sql injection. Remote exploitation of the at…

    code-projects BloodBank Managing System
  • High 7.5
    CVE-2026-4060 Public exploit

    Geo Mashup <= 1.13.18 - Unauthenticated Time-Based SQL Injection via 'sort' Parameter

    The Geo Mashup plugin for WordPress is vulnerable to Time-Based SQL Injection via the 'sort' parameter in all versions up to, and including, 1.13.18. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the…

    cyberhobo Geo Mashup Web / CMS
  • Medium 4.7
    CVE-2026-7394 Public exploit

    SourceCodester Pizzafy Ecommerce System GET Parameter view_order.php sql injection

    A vulnerability was determined in SourceCodester Pizzafy Ecommerce System 1.0. Affected by this vulnerability is an unknown functionality of the file /admin/view_order.php of the component GET Parameter Handler. Executing a manipulation of the argument ID can…

    SourceCodester Pizzafy Ecommerce System
  • Medium 6.3
    CVE-2026-7392 Public exploit

    SourceCodester Pharmacy Sales and Inventory System ajax.php delete_supplier sql injection

    A vulnerability has been found in SourceCodester Pharmacy Sales and Inventory System 1.0. This impacts the function delete_supplier of the file /ajax.php?action=delete_supplier. Such manipulation of the argument ID leads to sql injection. The attack can be ex…

    SourceCodester Pharmacy Sales and Inventory System
  • Medium 6.3
    CVE-2026-7229 Public exploit

    code-projects Coaching Management System POST reply.php sql injection

    A vulnerability was found in code-projects Coaching Management System 1.0. This affects an unknown function of the file /cims/modules/admin/reply.php of the component POST Handler. Performing a manipulation of the argument complaintreply results in sql inject…

    code-projects Coaching Management System
  • High 7.3
    CVE-2026-7228 Public exploit

    SourceCodester Pizzafy Ecommerce System ajax.php get_cart_count sql injection

    A flaw has been found in SourceCodester Pizzafy Ecommerce System 1.0. The affected element is the function get_cart_count of the file /admin/ajax.php?action=get_cart_count. This manipulation of the argument ID causes sql injection. The attack is possible to b…

    SourceCodester Pizzafy Ecommerce System
  • High 8.1
    CVE-2026-42167 Public exploit

    mod_sql in ProFTPD before 1.3.9a allows remote attackers to execute arbitrary code via a username, in scenarios where t…

    ProFTPD ProFTPD proftpd-dfsg proftpd-dfsg Debian Ubuntu Alpine
  • Critical 9.8
    CVE-2026-41462 Public exploit

    ProjeQtor < 12.4.4 Unauthenticated SQL Injection via Login

    ProjeQtor versions 7.0 through 12.4.3 contain an unauthenticated SQL injection vulnerability in the login functionality where the login variable is directly concatenated into a SQL query without parameterization or sanitization. Attackers can inject arbitrary…

    ProjeQtor ProjeQtor
  • High 7.3
    CVE-2026-7070 Public exploit

    code-projects Inventory Management System Login sql injection

    A weakness has been identified in code-projects Inventory Management System 1.0. Affected is an unknown function of the component Login. Executing a manipulation of the argument Username can lead to sql injection. The attack may be launched remotely. The expl…

    code-projects Inventory Management System
  • Critical 9.4
    CVE-2024-46636 Public exploit

    NASA Earth Observing System Data and Information System (EOSDIS) MODAPS v8.1 was discovered to contain a SQL injection …

  • Medium 4.7
    CVE-2026-7028 Public exploit

    CodeAstro Online Job Portal All Jobs delete-jobs.php sql injection

    A security flaw has been discovered in CodeAstro Online Job Portal 1.0. The affected element is an unknown function of the file /admin/jobs-admins/delete-jobs.php of the component All Jobs Page. Performing a manipulation of the argument ID results in sql inje…

    CodeAstro Online Job Portal
  • Critical 9.8
    CVE-2026-29198 Public exploit

    In Rocket.Chat <8.3.0, <8.2.1, <8.1.2, <8.0.3, <7.13.5, <7.12.6, <7.11.6, and <7.10.9, a NoSQL injection vulnerability …

    Rocket.Chat Rocket.Chat
  • Critical 9.8
    CVE-2026-37749 Public exploit

    A SQL injection vulnerability in CodeAstro Simple Attendance Management System v1.0 allows remote unauthenticated attac…

  • High 7.3
    CVE-2026-6183 Public exploit

    code-projects Simple Content Management System index.php sql injection

    A security flaw has been discovered in code-projects Simple Content Management System 1.0. Affected by this issue is some unknown functionality of the file /web/index.php. Performing a manipulation of the argument ID results in sql injection. Remote exploitat…

    code-projects Simple Content Management System
  • High 7.3
    CVE-2026-6182 Public exploit

    code-projects Simple Content Management System login.php sql injection

    A vulnerability was identified in code-projects Simple Content Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /web/admin/login.php. Such manipulation of the argument User leads to sql injection. The attack may be…

    code-projects Simple Content Management System
  • Critical 9.8
    CVE-2026-29861 Public exploit

    PHP-MYSQL-User-Login-System v1.0 was discovered to contain a SQL injection vulnerability via the username parameter at …