pg_partman is a PostgreSQL extension that manages partitioned tables by time or ID. Prior to 5.5.0, create_partition_time() reads the writable part_config.time_encoder text value and interpolates it without identifier quoting into a dynamically executed SELECT statement. A role with the documented partman_user INSERT and UPDATE privileges can store SQL rather than a function name. When pg_partman_bgw later creates a child partition for a text- or UUID-keyed set, the worker executes the stored SQL with pg_partman_bgw.role privileges, which default to PostgreSQL superuser. The persistent configuration row can repeatedly restore elevated access on later maintenance ticks, and successful exploitation can permit database-wide compromise and operating-system command execution as the PostgreSQL service account. This issue is fixed in version 5.5.0.
IBM Guardium Data Protection version 12.2 contains a critical SQL injection vulnerability that allows a remote authenticated attacker to execute arbitrary SQL commands. This flaw arises from improper neutralization of special elements in SQL commands, potentially leading to full compromise of confidentiality, integrity, and availability of the affected system.
IBM Guardium Data Protection version 12.2 contains a SQL injection vulnerability in the Analytic Grid Service Handler. This flaw allows a low-privileged authenticated user to inject SQL commands via the analytic cases grid endpoint, potentially leading to unauthorized access to sensitive data and impacting confidentiality, integrity, and availability of the system.
IBM Guardium Data Protection 12.2 contains a SQL injection vulnerability in the New Query Builder REST Processor. A low-privileged authenticated user can exploit this flaw via the newQueryBuilder REST endpoint to inject SQL commands. This may lead to unauthorized data access and compromise the confidentiality, integrity, and availability of the system.
IBM Guardium Data Protection 12.2 is vulnerable to a SQL injection vulnerability in the Load Balancer Groups component. An unauthenticated user can inject SQL statements through the Load Balancer Servlet endpoint, potentially resulting in unauthorized access to data and impact to the confidentiality, integrity, and availability of the affected system.
IBM Guardium Data Protection 12.2 is vulnerable to an unauthenticated second-order SQL injection vulnerability in the generateInsertQuery functionality of change-tracker-data.sql. A remote attacker could inject malicious SQL that is subsequently processed by the application, potentially resulting in compromise of the confidentiality, integrity, and availability of the affected system.
IBM Platform RTM, part of spectrum-lsf, is affected by a SQL injection vulnerability (CWE-89) that allows remote attackers to execute specially crafted SQL commands. This could enable unauthorized viewing, addition, modification, or deletion of data in the backend database. The vulnerability has a high severity with a CVSS score of 8.6. No specific affected versions or patch information is provided.
HCL BigFix Service Management is affected by SQL Injection flaw and a Cross-Tenant Data Exposure flaw vulnerabilities. which could allow an authenticated attacker to inject database commands to extract sensitive system details, as well as manipulate request values to gain unauthorized access to full personal profile data and PII across different organizations.
The Location Manager plugin for WordPress is vulnerable to generic SQL Injection via 'latitude' and 'longitude' REST API Parameters in all versions up to, and including, 2.3.38 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The injection is triggered when the orderby=lat_lon parameter is supplied, and affects multiple publicly accessible REST endpoints including geodir/v2/locations/cities, /regions, /countries, and /neighbourhoods via both the get_locations() and get_neighbourhoods() functions.
WP Multi Store Locator Pro plugin for WordPress versions up to 4.5.1 is vulnerable to an unauthenticated SQL Injection via the 'store_locatore_search_radius' parameter. The vulnerability arises from insufficient escaping and lack of query preparation, allowing attackers to inject additional SQL commands in a numeric, unquoted context. The AJAX handler is accessible without authentication or nonce verification, increasing exposure. This vulnerability can lead to unauthorized extraction of sensitive database information.
The Photo Gallery by 10Web – Mobile-Friendly Image Gallery plugin for WordPress is vulnerable to time-based SQL Injection via 'album_id' Shortcode Attribute in all versions up to, and including, 1.8.44 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with author-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. An Author-level user can store a SQL injection payload inside a published post's shortcode attribute, causing the payload to execute when any visitor renders the post; notably, the unsanitized value appears on both sides of a UNION query, potentially doubling the observable time-based delay.
NEX-Forms – Ultimate Forms Plugin for WordPress versions up to and including 9.3.0 contains an SQL Injection vulnerability via the 'additional_params' parameter. Authenticated users with custom-level access or higher can exploit this flaw to append malicious SQL queries, potentially extracting sensitive database information. The issue arises because input sanitization is insufficient and an operator allowlist is inconsistently applied, leaving the SQL query vulnerable.
The WP Inventory Manager plugin for WordPress is vulnerable to SQL Injection via the 'where' shortcode attribute of the [wpinventory] shortcode in versions up to, and including, 2.5.1. This is due to insufficient escaping on the user-supplied parameter and lack of sufficient preparation on the existing SQL query in the WPIMItem::get_all() function — parse_custom_where() only performs html_entity_decode(), strips semicolons, and does field-label name replacements, without using $wpdb->prepare() or a whitelist. The resulting string is concatenated into a raw SELECT statement that is executed via $wpdb->get_results(). This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
The WCFM Marketplace – Multivendor Marketplace for WooCommerce plugin for WordPress contains a SQL Injection vulnerability via the 'wcfmmp_user_location_lng' parameter in versions up to and including 3.8.2. This vulnerability allows unauthenticated attackers to inject SQL commands due to insufficient escaping and lack of proper query preparation. Exploitation can lead to unauthorized extraction of sensitive database information. The vulnerability has a high severity score of 7.5 and does not require user interaction or privileges to exploit.
The InfiniteWP Client plugin for WordPress is vulnerable to SQL Injection via the get_comments action in versions up to, and including, 1.13.9. This is due to insufficient escaping on the array-key names supplied in the JSON request body before use in a SQL statement: IWP_MMB_Comment::get_comments() calls extract() on $args (which silently skips keys that are not valid PHP variable names) but a second foreach($args as $checkbox => $checkbox_val) processes every key, strips the 'iwp_get_comments_' prefix with str_replace(), wraps the remainder in single quotes, and imploded it into an IN(...) clause that is executed via $wpdb->get_results() with no prepare(). Because the request body is read from php://input and JSON-decoded, wp_magic_quotes() never touches the data, so quote characters in keys pass through unaltered. This makes it possible for authenticated attackers, with administrator-level access and above (an administrator can register their own public key via add_site using the plugin's WP-admin-generated activation_key and then issue signed get_comments requests), to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
The Tz Weekly Radio Schedule WordPress plugin through 1.8.1 does not sanitize and escape a parameter before using it to build a SQL query on an AJAX action available to unauthenticated users, allowing unauthenticated attackers to perform SQL injection attacks and extract sensitive data from the database.
The Tz Weekly Radio Schedule WordPress plugin through 1.8.1 does not sanitize and escape a parameter before using it to build a SQL query on an AJAX action available to unauthenticated users, allowing unauthenticated attackers to perform SQL injection attacks and extract sensitive data from the database.
The Product Question and Answer WordPress plugin through 1.1.0 does not sanitize and escape parameters before using them in SQL queries on AJAX actions available to unauthenticated users, allowing unauthenticated attackers to perform SQL injection attacks and extract sensitive data from the database.
The Price Drop Alert for Woo Commerce WordPress plugin through 1.1 does not sanitize and escape parameters before using them in a SQL query on an AJAX action available to unauthenticated users, allowing unauthenticated attackers to perform SQL injection attacks and extract sensitive data from the database.
The wp shortcut link and advertisement baner WordPress plugin through 1.2.0 does not sanitize and escape a parameter before using it in a SQL query on an AJAX action available to unauthenticated users, allowing unauthenticated attackers to perform SQL injection attacks and extract sensitive data from the database.