Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach vulnerable module endpoint over network
-
ExploitSubmit input with crafted SQL payload
-
ExecutionBackend executes attacker-controlled SQL
-
ImpactExfiltrate sensitive database records
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The vulnerable amazee.ai Private AI Provider module (versions 0.0.0 through 1.3.7, or 1.4.0 through 1.4.3) must be installed and enabled on a Drupal site. Per the CVSS vector the vector is remote and requires no privileges (PR:N) and no user interaction (UI:N), but the vector rates attack complexity as high (AC:H) and the specific feature, endpoint, or input parameter that carries the injection is not described in the available sources, so the precise trigger condition cannot be confirmed. Limiting factors: this is a contrib module that most Drupal sites do not install, bounding exposure to the subset running affected versions; and the unauthenticated (PR:N) claim is taken from the CVSS vector only and is not corroborated by the description, which many Drupal contrib SQLi issues would qualify with a required permission. |
| Impact | This is a medium-severity SQL injection (CWE-89, base CVSS 6.5) in the amazee.ai Private AI Provider Drupal contrib module. The supplied CVSS vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N) indicates a network-reachable, nominally unauthenticated flaw whose primary consequence is confidentiality loss (C:H) with only limited integrity impact and no availability impact - consistent with an attacker reading database contents rather than fully taking over the system. The exploitation signals argue against treating this as an emergency: EPSS is only 0.17% (6th percentile), the CVE is NOT on CISA KEV, and no public exploit or PoC reference is present beyond the vendor advisory. The vuln.today decision label is 'this_month' (not act_now/emergency), aligning with 'patch on your normal cycle' rather than drop-everything urgency. Two points warrant verification: (1) the vector asserts AC:H but the description gives no trigger detail, so the basis for high attack complexity is not stated in the available sources; and (2) the vector asserts PR:N (unauthenticated), yet many Drupal contrib SQLi flaws require an account with a specific permission - authentication requirement is taken from the CVSS vector only and is not independently confirmed by the description. Net: a real but non-urgent, data-disclosure-focused issue in a niche module; prioritize patching this month. |
| Exploit ScenarioDerived | An attacker who can reach a Drupal site running a vulnerable amazee.ai Private AI Provider version (0.0.0-1.3.7 or 1.4.0-1.4.3) submits input to the affected module feature that is concatenated into a backend SQL query, injecting their own SQL to read sensitive rows from the Drupal database. Per the CVSS vector the vector is network-based and requires no privileges, though the vector also rates attack complexity as high; the specific injectable parameter and the reason for that complexity are not described in the available sources. No public exploit code or PoC reference is present at the time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 22, 2026
SQL injection (CWE-89, base CVSS 6.5) in the amazee.ai Private AI Provider Drupal contrib module lets an attacker inject into SQL statements executed by the module's database layer, with high confidentiality impact and limited integrity impact in the assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N). Every site running the module in versions 0.0.0 through 1.3.7, or 1.4.0 through 1.4.3, is affected; exposure is bounded because this is a contrib module that most Drupal installations do not deploy. No confirmed active exploitation (not in CISA KEV) and no public exploit code were identified at time of analysis, and EPSS is low at 0.17% (6th percentile), but the vendor has published a security advisory and a patched release, and the standard Drupal contrib upgrade path applies. Note the published CVE vector scores PR:N while the independent assessment scores PR:L, so the privilege level an attacker needs is not consistently confirmed across sources.
RemediationAI
A vendor patch is available per the Drupal security advisory at https://www.drupal.org/sa-contrib-2026-134, which is the authoritative source for the exact fixed release numbers in each branch; affected ranges terminate at 1.3.7 in the 1.x line and 1.4.3 in the 1.4 line, so sites should update to the patched release the advisory names for their branch rather than remain on any version inside those ranges, and the two branches should be tracked separately because the 1.4 line was forked and patched independently. Where an update cannot be applied in the current maintenance window (the reported priority places this in the this-month cadence rather than emergency patching, consistent with the low EPSS score and absence of confirmed exploitation), the most direct compensating control is to disable or uninstall the amazee.ai Private AI Provider module until the upgrade can be performed, which removes the injectable code path entirely at the cost of losing the private AI provider functionality the module supplies; no narrower workaround, endpoint restriction, or configuration toggle is documented in the available sources. After upgrading, confirm the deployed version by checking the module's info file or the site's available updates report, since Drupal will not flag the module as insecure until the release metadata is refreshed.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in composer, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a classic SQL injection (CWE-89) in a PHP-based Drupal contributed module, meaning special elements in an SQL command are not neutralized before the query reaches the database. Drupal's database abstraction layer still requires callers to use placeholders and query builders correctly, so a contrib module that concatenates values into a query exposes the underlying MySQL/MariaDB or PostgreSQL backend. The CPE identifier cpe:2.3:a:drupal:amazee.ai_private_ai_provider confirms the package scope as the Drupal contrib project rather than Drupal core, and the flaw ships in two affected release lines (0.0.0 through 1.3.7 and 1.4.0 through 1.4.3). The specific feature, endpoint, or input parameter that carries the injection is not described in the available sources, so the precise trigger condition cannot be confirmed; the published vector additionally rates attack complexity as high, but no source states what condition makes exploitation complex. The published vector (PR:N) and the independent assessment (PR:L) disagree on whether authentication is required, and the description does not corroborate either, so the actual permission needed to reach the injectable code path remains unverified.
Know when Amazee Ai Private Ai Provider gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
Network SQLi with no trigger detail defaults to AC:L; Drupal contrib access typically needs an authenticated role, so PR:L; impact is mainly data disclosure (C:H), limited integrity, no availability.
Primary rating from Vendor (drupal).
CVSS VectorVendor: drupal
Lifecycle Timeline
3DescriptionCVE.org
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Drupal amazee.ai Private AI Provider allows SQL Injection. This issue affects amazee.ai Private AI Provider versions: from 0.0.0 to 1.3.7, from 1.4.0 to 1.4.3.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
EUVD-2026-107865
GHSA-28qc-3cgq-p54x
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB