CWE-89
AllowedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Abstraction: Base · Status: Stable
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.
28333 vulnerabilities reference this CWE, most recent first.
GHSA-8CP6-C94H-9538
Vulnerability from github – Published: 2026-08-19 15:32 – Updated: 2026-08-19 15:32Dell OpenManage Enterprise, versions prior to 4.7.0, contains an Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to Information exposure.
{
"affected": [],
"aliases": [
"CVE-2026-71176"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-19T15:18:01Z",
"severity": "HIGH"
},
"details": "Dell OpenManage Enterprise, versions prior to 4.7.0, contains an Improper Neutralization of Special Elements used in an SQL Command (\u0027SQL Injection\u0027) vulnerability. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to Information exposure.",
"id": "GHSA-8cp6-c94h-9538",
"modified": "2026-08-19T15:32:39Z",
"published": "2026-08-19T15:32:39Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-71176"
},
{
"type": "WEB",
"url": "https://www.dell.com/support/kbdoc/en-us/000500910/dsa-2026-359-security-update-for-dell-openmanage-enterprise-vulnerabilities"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-8CPG-WMQX-MHP9
Vulnerability from github – Published: 2023-03-08 18:30 – Updated: 2023-03-14 18:30SQL injection vulnerability found in Varisicte matrix-gui v.2 allows a remote attacker to execute arbitrary code via the shell_exect parameter to the \www\pages\matrix-gui-2.0 endpoint.
{
"affected": [],
"aliases": [
"CVE-2023-26922"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-03-08T16:15:00Z",
"severity": "CRITICAL"
},
"details": "SQL injection vulnerability found in Varisicte matrix-gui v.2 allows a remote attacker to execute arbitrary code via the shell_exect parameter to the \\www\\pages\\matrix-gui-2.0 endpoint.",
"id": "GHSA-8cpg-wmqx-mhp9",
"modified": "2023-03-14T18:30:27Z",
"published": "2023-03-08T18:30:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-26922"
},
{
"type": "WEB",
"url": "https://github.com/varigit/matrix-gui-v2/issues/1"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-8CPJ-V5F7-G2FM
Vulnerability from github – Published: 2022-09-21 00:00 – Updated: 2022-09-22 00:00Vulnerabilities in the web-based management interface of ClearPass Policy Manager could allow an authenticated remote attacker to conduct SQL injection attacks against the ClearPass Policy Manager instance. An attacker could exploit these vulnerabilities to obtain and modify sensitive information in the underlying database potentially leading to complete compromise of the ClearPass Policy Manager cluster in Aruba ClearPass Policy Manager version(s): 6.10.x: 6.10.6 and below; 6.9.x: 6.9.11 and below. Aruba has released upgrades for Aruba ClearPass Policy Manager that address these security vulnerabilities.
{
"affected": [],
"aliases": [
"CVE-2022-23695"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-09-20T21:15:00Z",
"severity": "HIGH"
},
"details": "Vulnerabilities in the web-based management interface of ClearPass Policy Manager could allow an authenticated remote attacker to conduct SQL injection attacks against the ClearPass Policy Manager instance. An attacker could exploit these vulnerabilities to obtain and modify sensitive information in the underlying database potentially leading to complete compromise of the ClearPass Policy Manager cluster in Aruba ClearPass Policy Manager version(s): 6.10.x: 6.10.6 and below; 6.9.x: 6.9.11 and below. Aruba has released upgrades for Aruba ClearPass Policy Manager that address these security vulnerabilities.",
"id": "GHSA-8cpj-v5f7-g2fm",
"modified": "2022-09-22T00:00:23Z",
"published": "2022-09-21T00:00:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-23695"
},
{
"type": "WEB",
"url": "https://www.arubanetworks.com/assets/alert/ARUBA-PSA-2022-013.txt"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-8CPQ-38P9-67GX
Vulnerability from github – Published: 2026-03-20 20:48 – Updated: 2026-03-27 20:57Summary
Kysely's DefaultQueryCompiler.sanitizeStringLiteral() only escapes single quotes by doubling them (' → '') but does not escape backslashes. When used with the MySQL dialect (where NO_BACKSLASH_ESCAPES is OFF by default), an attacker can use a backslash to escape the trailing quote of a string literal, breaking out of the string context and injecting arbitrary SQL. This affects any code path that uses ImmediateValueTransformer to inline values — specifically CreateIndexBuilder.where() and CreateViewBuilder.as().
Details
The root cause is in DefaultQueryCompiler.sanitizeStringLiteral():
src/query-compiler/default-query-compiler.ts:1819-1821
protected sanitizeStringLiteral(value: string): string {
return value.replace(LIT_WRAP_REGEX, "''")
}
Where LIT_WRAP_REGEX is defined as /'/g (line 121). This only doubles single quotes — it does not escape backslash characters.
The function is called from appendStringLiteral() which wraps the sanitized value in single quotes:
src/query-compiler/default-query-compiler.ts:1841-1845
protected appendStringLiteral(value: string): void {
this.append("'")
this.append(this.sanitizeStringLiteral(value))
this.append("'")
}
This is reached when visitValue() encounters an immediate value node (line 525-527), which is created by ImmediateValueTransformer used in CreateIndexBuilder.where():
src/schema/create-index-builder.ts:266-278
where(...args: any[]): any {
const transformer = new ImmediateValueTransformer()
return new CreateIndexBuilder({
...this.#props,
node: QueryNode.cloneWithWhere(
this.#props.node,
transformer.transformNode(
parseValueBinaryOperationOrExpression(args),
this.#props.queryId,
),
),
})
}
The MysqlQueryCompiler (at src/dialect/mysql/mysql-query-compiler.ts:6-75) extends DefaultQueryCompiler but does not override sanitizeStringLiteral, inheriting the backslash-unaware implementation.
Exploitation mechanism:
In MySQL with the default NO_BACKSLASH_ESCAPES=OFF setting, the backslash character (\) acts as an escape character inside string literals. Given input \' OR 1=1 --:
sanitizeStringLiteraldoubles the quote:\'' OR 1=1 --appendStringLiteralwraps:'\'' OR 1=1 --'- MySQL interprets
\'as an escaped (literal) single quote, so the string content is'and the second'closes the string OR 1=1 --is parsed as SQL
PoC
import { Kysely, MysqlDialect } from 'kysely'
import { createPool } from 'mysql2'
interface Database {
orders: {
id: number
status: string
order_nr: string
}
}
const db = new Kysely<Database>({
dialect: new MysqlDialect({
pool: createPool({
host: 'localhost',
database: 'test',
user: 'root',
password: 'password',
}),
}),
})
// Simulates user-controlled input reaching CreateIndexBuilder.where()
const userInput = "\\' OR 1=1 --"
const query = db.schema
.createIndex('orders_status_index')
.on('orders')
.column('status')
.where('status', '=', userInput)
// Compile to see the generated SQL
const compiled = query.compile()
console.log(compiled.sql)
// Output: create index `orders_status_index` on `orders` (`status`) where `status` = '\'' OR 1=1 --'
//
// MySQL parses this as:
// WHERE `status` = '\' ← string literal containing a single quote
// ' OR 1=1 --' ← injected SQL (OR 1=1), comment eats trailing quote
To verify against a live MySQL instance:
-- Setup
CREATE DATABASE test;
USE test;
CREATE TABLE orders (id INT PRIMARY KEY, status VARCHAR(50), order_nr VARCHAR(50));
INSERT INTO orders VALUES (1, 'active', '001'), (2, 'cancelled', '002');
-- The compiled query from Kysely with injected payload:
-- This returns all rows instead of filtering by status
SELECT * FROM orders WHERE status = '\'' OR 1=1 -- ';
Impact
- SQL Injection: An attacker who controls values passed to
CreateIndexBuilder.where()orCreateViewBuilder.as()can inject arbitrary SQL statements when the application uses the MySQL dialect. - Data Exfiltration: Injected SQL can read arbitrary data from the database using UNION-based or subquery-based techniques.
- Data Modification/Destruction: Stacked queries or subqueries can modify or delete data.
- Authentication Bypass: If index creation or view definitions are influenced by user input in application logic, the injection can alter query semantics to bypass access controls.
The attack complexity is rated High (AC:H) because exploitation requires an application to pass untrusted user input into DDL schema builder methods, which is an atypical but not impossible usage pattern. The CreateIndexBuilder.where() docstring (line 247) notes "Parameters are always sent as literals due to database restrictions" without warning about the security implications.
Recommended Fix
MysqlQueryCompiler should override sanitizeStringLiteral to escape backslashes before doubling quotes:
src/dialect/mysql/mysql-query-compiler.ts
const LIT_WRAP_REGEX = /'/g
const BACKSLASH_REGEX = /\\/g
export class MysqlQueryCompiler extends DefaultQueryCompiler {
// ... existing overrides ...
protected override sanitizeStringLiteral(value: string): string {
// Escape backslashes first (\ → \\), then double single quotes (' → '')
// MySQL treats backslash as an escape character by default (NO_BACKSLASH_ESCAPES=OFF)
return value.replace(BACKSLASH_REGEX, '\\\\').replace(LIT_WRAP_REGEX, "''")
}
}
Alternatively, the library could use parameterized queries for these DDL builders where the database supports it, avoiding string literal interpolation entirely. For databases that don't support parameters in DDL statements, the dialect-specific compiler must escape all characters that have special meaning in that dialect's string literal syntax.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 0.28.13"
},
"package": {
"ecosystem": "npm",
"name": "kysely"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.28.14"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-33468"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-20T20:48:55Z",
"nvd_published_at": "2026-03-26T17:16:41Z",
"severity": "HIGH"
},
"details": "## Summary\n\nKysely\u0027s `DefaultQueryCompiler.sanitizeStringLiteral()` only escapes single quotes by doubling them (`\u0027` \u2192 `\u0027\u0027`) but does not escape backslashes. When used with the MySQL dialect (where `NO_BACKSLASH_ESCAPES` is OFF by default), an attacker can use a backslash to escape the trailing quote of a string literal, breaking out of the string context and injecting arbitrary SQL. This affects any code path that uses `ImmediateValueTransformer` to inline values \u2014 specifically `CreateIndexBuilder.where()` and `CreateViewBuilder.as()`.\n\n## Details\n\nThe root cause is in `DefaultQueryCompiler.sanitizeStringLiteral()`:\n\n**`src/query-compiler/default-query-compiler.ts:1819-1821`**\n```typescript\nprotected sanitizeStringLiteral(value: string): string {\n return value.replace(LIT_WRAP_REGEX, \"\u0027\u0027\")\n}\n```\n\nWhere `LIT_WRAP_REGEX` is defined as `/\u0027/g` (line 121). This only doubles single quotes \u2014 it does not escape backslash characters.\n\nThe function is called from `appendStringLiteral()` which wraps the sanitized value in single quotes:\n\n**`src/query-compiler/default-query-compiler.ts:1841-1845`**\n```typescript\nprotected appendStringLiteral(value: string): void {\n this.append(\"\u0027\")\n this.append(this.sanitizeStringLiteral(value))\n this.append(\"\u0027\")\n}\n```\n\nThis is reached when `visitValue()` encounters an immediate value node (line 525-527), which is created by `ImmediateValueTransformer` used in `CreateIndexBuilder.where()`:\n\n**`src/schema/create-index-builder.ts:266-278`**\n```typescript\nwhere(...args: any[]): any {\n const transformer = new ImmediateValueTransformer()\n\n return new CreateIndexBuilder({\n ...this.#props,\n node: QueryNode.cloneWithWhere(\n this.#props.node,\n transformer.transformNode(\n parseValueBinaryOperationOrExpression(args),\n this.#props.queryId,\n ),\n ),\n })\n}\n```\n\nThe `MysqlQueryCompiler` (at `src/dialect/mysql/mysql-query-compiler.ts:6-75`) extends `DefaultQueryCompiler` but does **not** override `sanitizeStringLiteral`, inheriting the backslash-unaware implementation.\n\n**Exploitation mechanism:**\n\nIn MySQL with the default `NO_BACKSLASH_ESCAPES=OFF` setting, the backslash character (`\\`) acts as an escape character inside string literals. Given input `\\\u0027 OR 1=1 --`:\n\n1. `sanitizeStringLiteral` doubles the quote: `\\\u0027\u0027 OR 1=1 --`\n2. `appendStringLiteral` wraps: `\u0027\\\u0027\u0027 OR 1=1 --\u0027`\n3. MySQL interprets `\\\u0027` as an escaped (literal) single quote, so the string content is `\u0027` and the second `\u0027` closes the string\n4. ` OR 1=1 --` is parsed as SQL\n\n## PoC\n\n```typescript\nimport { Kysely, MysqlDialect } from \u0027kysely\u0027\nimport { createPool } from \u0027mysql2\u0027\n\ninterface Database {\n orders: {\n id: number\n status: string\n order_nr: string\n }\n}\n\nconst db = new Kysely\u003cDatabase\u003e({\n dialect: new MysqlDialect({\n pool: createPool({\n host: \u0027localhost\u0027,\n database: \u0027test\u0027,\n user: \u0027root\u0027,\n password: \u0027password\u0027,\n }),\n }),\n})\n\n// Simulates user-controlled input reaching CreateIndexBuilder.where()\nconst userInput = \"\\\\\u0027 OR 1=1 --\"\n\nconst query = db.schema\n .createIndex(\u0027orders_status_index\u0027)\n .on(\u0027orders\u0027)\n .column(\u0027status\u0027)\n .where(\u0027status\u0027, \u0027=\u0027, userInput)\n\n// Compile to see the generated SQL\nconst compiled = query.compile()\nconsole.log(compiled.sql)\n// Output: create index `orders_status_index` on `orders` (`status`) where `status` = \u0027\\\u0027\u0027 OR 1=1 --\u0027\n//\n// MySQL parses this as:\n// WHERE `status` = \u0027\\\u0027 \u2190 string literal containing a single quote\n// \u0027 OR 1=1 --\u0027 \u2190 injected SQL (OR 1=1), comment eats trailing quote\n```\n\nTo verify against a live MySQL instance:\n\n```sql\n-- Setup\nCREATE DATABASE test;\nUSE test;\nCREATE TABLE orders (id INT PRIMARY KEY, status VARCHAR(50), order_nr VARCHAR(50));\nINSERT INTO orders VALUES (1, \u0027active\u0027, \u0027001\u0027), (2, \u0027cancelled\u0027, \u0027002\u0027);\n\n-- The compiled query from Kysely with injected payload:\n-- This returns all rows instead of filtering by status\nSELECT * FROM orders WHERE status = \u0027\\\u0027\u0027 OR 1=1 -- \u0027;\n```\n\n## Impact\n\n- **SQL Injection:** An attacker who controls values passed to `CreateIndexBuilder.where()` or `CreateViewBuilder.as()` can inject arbitrary SQL statements when the application uses the MySQL dialect.\n- **Data Exfiltration:** Injected SQL can read arbitrary data from the database using UNION-based or subquery-based techniques.\n- **Data Modification/Destruction:** Stacked queries or subqueries can modify or delete data.\n- **Authentication Bypass:** If index creation or view definitions are influenced by user input in application logic, the injection can alter query semantics to bypass access controls.\n\nThe attack complexity is rated High (AC:H) because exploitation requires an application to pass untrusted user input into DDL schema builder methods, which is an atypical but not impossible usage pattern. The `CreateIndexBuilder.where()` docstring (line 247) notes \"Parameters are always sent as literals due to database restrictions\" without warning about the security implications.\n\n## Recommended Fix\n\n`MysqlQueryCompiler` should override `sanitizeStringLiteral` to escape backslashes before doubling quotes:\n\n**`src/dialect/mysql/mysql-query-compiler.ts`**\n```typescript\nconst LIT_WRAP_REGEX = /\u0027/g\nconst BACKSLASH_REGEX = /\\\\/g\n\nexport class MysqlQueryCompiler extends DefaultQueryCompiler {\n // ... existing overrides ...\n\n protected override sanitizeStringLiteral(value: string): string {\n // Escape backslashes first (\\ \u2192 \\\\), then double single quotes (\u0027 \u2192 \u0027\u0027)\n // MySQL treats backslash as an escape character by default (NO_BACKSLASH_ESCAPES=OFF)\n return value.replace(BACKSLASH_REGEX, \u0027\\\\\\\\\u0027).replace(LIT_WRAP_REGEX, \"\u0027\u0027\")\n }\n}\n```\n\nAlternatively, the library could use parameterized queries for these DDL builders where the database supports it, avoiding string literal interpolation entirely. For databases that don\u0027t support parameters in DDL statements, the dialect-specific compiler must escape all characters that have special meaning in that dialect\u0027s string literal syntax.",
"id": "GHSA-8cpq-38p9-67gx",
"modified": "2026-03-27T20:57:32Z",
"published": "2026-03-20T20:48:55Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/kysely-org/kysely/security/advisories/GHSA-8cpq-38p9-67gx"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-33468"
},
{
"type": "PACKAGE",
"url": "https://github.com/kysely-org/kysely"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "Kysely has a MySQL SQL Injection via Insufficient Backslash Escaping in `sql.lit(string)` usage or similar methods that append string literal values into the compiled SQL strings"
}
GHSA-8CR3-2G2W-J5M2
Vulnerability from github – Published: 2024-11-23 15:32 – Updated: 2024-11-23 15:32A vulnerability was found in code-projects Simple Car Rental System 1.0. It has been classified as critical. Affected is an unknown function of the file /book_car.php. The manipulation of the argument fname/id_no/gender/email/phone/location leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The initial researcher advisory only mentions the parameter "fname" to be affected. Further analysis indicates that other arguments might be affected as well.
{
"affected": [],
"aliases": [
"CVE-2024-11632"
],
"database_specific": {
"cwe_ids": [
"CWE-74",
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-11-23T14:15:17Z",
"severity": "MODERATE"
},
"details": "A vulnerability was found in code-projects Simple Car Rental System 1.0. It has been classified as critical. Affected is an unknown function of the file /book_car.php. The manipulation of the argument fname/id_no/gender/email/phone/location leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The initial researcher advisory only mentions the parameter \"fname\" to be affected. Further analysis indicates that other arguments might be affected as well.",
"id": "GHSA-8cr3-2g2w-j5m2",
"modified": "2024-11-23T15:32:27Z",
"published": "2024-11-23T15:32:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-11632"
},
{
"type": "WEB",
"url": "https://github.com/sil3n/cve/issues/2"
},
{
"type": "WEB",
"url": "https://code-projects.org"
},
{
"type": "WEB",
"url": "https://vuldb.com/?ctiid.285918"
},
{
"type": "WEB",
"url": "https://vuldb.com/?id.285918"
},
{
"type": "WEB",
"url": "https://vuldb.com/?submit.446308"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-8CR5-WJQG-R3M8
Vulnerability from github – Published: 2022-05-02 06:18 – Updated: 2022-05-02 06:18SQL injection vulnerability in index.php in MASA2EL Music City 1.0 and 1.1 allows remote attackers to execute arbitrary SQL commands via the id parameter in a singer action.
{
"affected": [],
"aliases": [
"CVE-2010-1047"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2010-03-23T01:00:00Z",
"severity": "HIGH"
},
"details": "SQL injection vulnerability in index.php in MASA2EL Music City 1.0 and 1.1 allows remote attackers to execute arbitrary SQL commands via the id parameter in a singer action.",
"id": "GHSA-8cr5-wjqg-r3m8",
"modified": "2022-05-02T06:18:25Z",
"published": "2022-05-02T06:18:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2010-1047"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/56110"
},
{
"type": "WEB",
"url": "http://osvdb.org/62133"
},
{
"type": "WEB",
"url": "http://packetstormsecurity.org/1002-exploits/masa2elmc-sql.txt"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/38469"
},
{
"type": "WEB",
"url": "http://www.exploit-db.com/exploits/11329"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-8CR8-VPQ4-H3W4
Vulnerability from github – Published: 2022-05-17 03:56 – Updated: 2022-05-17 03:56SQL injection vulnerability in Ecava IntegraXor before 5.0 build 4522 allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors.
{
"affected": [],
"aliases": [
"CVE-2016-2301"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2016-04-22T00:59:00Z",
"severity": "MODERATE"
},
"details": "SQL injection vulnerability in Ecava IntegraXor before 5.0 build 4522 allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors.",
"id": "GHSA-8cr8-vpq4-h3w4",
"modified": "2022-05-17T03:56:26Z",
"published": "2022-05-17T03:56:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2016-2301"
},
{
"type": "WEB",
"url": "https://ics-cert.us-cert.gov/advisories/ICSA-16-105-03"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-8CR9-RQ58-W482
Vulnerability from github – Published: 2021-12-04 00:00 – Updated: 2021-12-05 00:00Taocms v2.5Beta5 was discovered to contain a blind SQL injection vulnerability via the function Article Search.
{
"affected": [],
"aliases": [
"CVE-2021-25783"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-12-02T23:15:00Z",
"severity": "HIGH"
},
"details": "Taocms v2.5Beta5 was discovered to contain a blind SQL injection vulnerability via the function Article Search.",
"id": "GHSA-8cr9-rq58-w482",
"modified": "2021-12-05T00:00:37Z",
"published": "2021-12-04T00:00:54Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-25783"
},
{
"type": "WEB",
"url": "https://github.com/taogogo/taocms/issues/5"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-8CRG-9WVR-72VM
Vulnerability from github – Published: 2023-12-25 03:30 – Updated: 2025-03-04 18:33A vulnerability, which was classified as critical, was found in PHPGurukul Restaurant Table Booking System 1.0. Affected is an unknown function of the file /admin/bwdates-report-details.php. The manipulation of the argument fdate leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-248952.
{
"affected": [],
"aliases": [
"CVE-2023-7100"
],
"database_specific": {
"cwe_ids": [
"CWE-74",
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-12-25T03:15:08Z",
"severity": "MODERATE"
},
"details": "A vulnerability, which was classified as critical, was found in PHPGurukul Restaurant Table Booking System 1.0. Affected is an unknown function of the file /admin/bwdates-report-details.php. The manipulation of the argument fdate leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-248952.",
"id": "GHSA-8crg-9wvr-72vm",
"modified": "2025-03-04T18:33:19Z",
"published": "2023-12-25T03:30:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-7100"
},
{
"type": "WEB",
"url": "https://medium.com/@2839549219ljk/restaurant-table-booking-system-sql-injection-vulnerability-30708cfabe03"
},
{
"type": "WEB",
"url": "https://phpgurukul.com"
},
{
"type": "WEB",
"url": "https://vuldb.com/?ctiid.248952"
},
{
"type": "WEB",
"url": "https://vuldb.com/?id.248952"
},
{
"type": "WEB",
"url": "https://vuldb.com/?submit.256861"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-8CRQ-7XW5-3644
Vulnerability from github – Published: 2022-05-01 23:49 – Updated: 2022-05-01 23:49SQL injection vulnerability in index.php in SazCart 1.5.1 and earlier, when magic_quotes_gpc is disabled, allows remote attackers to execute arbitrary SQL commands via the prodid parameter in a details action.
{
"affected": [],
"aliases": [
"CVE-2008-2411"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2008-05-22T13:09:00Z",
"severity": "MODERATE"
},
"details": "SQL injection vulnerability in index.php in SazCart 1.5.1 and earlier, when magic_quotes_gpc is disabled, allows remote attackers to execute arbitrary SQL commands via the prodid parameter in a details action.",
"id": "GHSA-8crq-7xw5-3644",
"modified": "2022-05-01T23:49:52Z",
"published": "2022-05-01T23:49:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2008-2411"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/42542"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/5576"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/30148"
},
{
"type": "WEB",
"url": "http://securityreason.com/securityalert/3900"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/archive/1/491892/100/0/threaded"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/29129"
}
],
"schema_version": "1.4.0",
"severity": []
}
Mitigation MIT-4
Strategy: Libraries or Frameworks
- 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.
Mitigation MIT-27
Strategy: Parameterization
- 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]
Mitigation MIT-17
Strategy: Environment Hardening
- 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.
Mitigation MIT-15
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.
Mitigation MIT-28
Strategy: Output Encoding
- 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.
Mitigation MIT-5
Strategy: Input Validation
- 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.
Mitigation MIT-21
Strategy: Enforcement by Conversion
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.
Mitigation MIT-39
- 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.
Mitigation MIT-29
Strategy: Firewall
Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth [REF-1481.
Mitigation MIT-16
Strategy: Environment Hardening
When using PHP, configure the application so that it does not use register_globals. During implementation, develop the application so that it does not rely on this feature, but be wary of implementing a register_globals emulation that is subject to weaknesses such as CWE-95, CWE-621, and similar issues.
CAPEC-108: Command Line Execution through SQL Injection
An attacker uses standard SQL injection methods to inject data into the command line for execution. This could be done directly through misuse of directives such as MSSQL_xp_cmdshell or indirectly through injection of data into the database that would be interpreted as shell commands. Sometime later, an unscrupulous backend application (or could be part of the functionality of the same application) fetches the injected data stored in the database and uses this data as command line arguments without performing proper validation. The malicious data escapes that data plane by spawning new commands to be executed on the host.
CAPEC-109: Object Relational Mapping Injection
An attacker leverages a weakness present in the database access layer code generated with an Object Relational Mapping (ORM) tool or a weakness in the way that a developer used a persistence framework to inject their own SQL commands to be executed against the underlying database. The attack here is similar to plain SQL injection, except that the application does not use JDBC to directly talk to the database, but instead it uses a data access layer generated by an ORM tool or framework (e.g. Hibernate). While most of the time code generated by an ORM tool contains safe access methods that are immune to SQL injection, sometimes either due to some weakness in the generated code or due to the fact that the developer failed to use the generated access methods properly, SQL injection is still possible.
CAPEC-110: SQL Injection through SOAP Parameter Tampering
An attacker modifies the parameters of the SOAP message that is sent from the service consumer to the service provider to initiate a SQL injection attack. On the service provider side, the SOAP message is parsed and parameters are not properly validated before being used to access a database in a way that does not use parameter binding, thus enabling the attacker to control the structure of the executed SQL query. This pattern describes a SQL injection attack with the delivery mechanism being a SOAP message.
CAPEC-470: Expanding Control over the Operating System from the Database
An attacker is able to leverage access gained to the database to read / write data to the file system, compromise the operating system, create a tunnel for accessing the host machine, and use this access to potentially attack other machines on the same network as the database machine. Traditionally SQL injections attacks are viewed as a way to gain unauthorized read access to the data stored in the database, modify the data in the database, delete the data, etc. However, almost every data base management system (DBMS) system includes facilities that if compromised allow an attacker complete access to the file system, operating system, and full access to the host running the database. The attacker can then use this privileged access to launch subsequent attacks. These facilities include dropping into a command shell, creating user defined functions that can call system level libraries present on the host machine, stored procedures, etc.
CAPEC-66: SQL Injection
This attack exploits target software that constructs SQL statements based on user input. An attacker crafts input strings so that when the target software constructs SQL statements based on the input, the resulting SQL statement performs actions other than those the application intended. SQL Injection results from failure of the application to appropriately validate input.
CAPEC-7: Blind SQL Injection
Blind SQL Injection results from an insufficient mitigation for SQL Injection. Although suppressing database error messages are considered best practice, the suppression alone is not sufficient to prevent SQL Injection. Blind SQL Injection is a form of SQL Injection that overcomes the lack of error messages. Without the error messages that facilitate SQL Injection, the adversary constructs input strings that probe the target through simple Boolean SQL expressions. The adversary can determine if the syntax and structure of the injection was successful based on whether the query was executed or not. Applied iteratively, the adversary determines how and where the target is vulnerable to SQL Injection.