Skip to main content

MySQL EUVDEUVD-2026-12138

| CVE-2026-32628 HIGH
SQL Injection (CWE-89)
2026-03-13 GitHub_M
7.7
CVSS 4.0 · GitHub Advisory
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticated user invokes SQL Agent plugin
  2. Exploit
    Supply malicious table_name parameter
  3. Execution
    getTableSchemaSql() concatenates unsanitized input
  4. Impact
    Execute arbitrary SQL on connected database

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

User must have valid AnythingLLM authentication credentials to invoke the SQL Agent plugin. The SQL Agent plugin must be enabled and configured with active database connections (MySQL, PostgreSQL, or MSSQL). Affects AnythingLLM versions 1.11.1 and earlier.

Impact

Despite the high CVSS score of 7.7, this vulnerability presents moderate real-world risk due to several mitigating factors. The attack vector is network-based but requires high attack complexity (AC:H) and present attack requirements (AT:P), suggesting specific conditions must be met for exploitation. Authentication is required (PR:L), limiting the attack surface to users who already have legitimate access to invoke the SQL Agent. The vulnerability is not listed in CISA KEV, indicating no known active exploitation in the wild. Without EPSS data or public POCs available, the immediate exploitation risk appears lower than the CVSS score suggests. However, the potential for high impact across confidentiality, integrity, and availability (VC:H/VI:H/VA:H) means organizations using AnythingLLM with database connections should prioritize remediation.

Exploit ScenarioDerived

An authenticated attacker with access to AnythingLLM could craft malicious table names containing SQL injection payloads when invoking the SQL Agent to query database schemas. By manipulating the table_name parameter passed to getTableSchemaSql(), the attacker could execute arbitrary SQL commands such as extracting sensitive data, modifying records, or potentially gaining deeper system access depending on database permissions. The high attack complexity suggests the attacker would need specific knowledge of the application's database structure and potentially chain multiple requests to achieve meaningful exploitation.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 13, 2026

SQL injection in AnythingLLM versions 1.11.1 and earlier enables authenticated users to execute arbitrary SQL commands against connected PostgreSQL, MySQL, and MSSQL databases through the built-in SQL Agent plugin. The vulnerability stems from unsafe string concatenation of table names in the getTableSchemaSql() method across all three database connectors, bypassing proper parameterization. Any user with access to invoke the SQL Agent can exploit this to read, modify, or delete sensitive database contents.

Earlier versions of this analysis (1)
v1 Mar 13, 2026 - 22:01 CVSS 7.7

A SQL injection vulnerability in AnythingLLM's SQL Agent plugin (versions 1.11.1 and earlier) allows authenticated users to execute arbitrary SQL commands on connected databases through unsanitized table_name parameters. The vulnerability affects MySQL, PostgreSQL, and MSSQL database connectors and has a CVSS 4.0 score of 7.7, requiring low privileges but potentially leading to full database compromise. No active exploitation has been reported (not in KEV), and no public proof-of-concept is currently available.

RemediationAI

Upgrade AnythingLLM to a version newer than 1.11.1 as soon as possible to address this SQL injection vulnerability. Until patching is complete, consider temporarily disabling the SQL Agent plugin functionality or restricting access to only highly trusted users who require this capability. Implement database activity monitoring to detect potential SQL injection attempts, and ensure database accounts used by AnythingLLM follow the principle of least privilege. Review and audit any recent SQL Agent usage logs for suspicious queries that may indicate exploitation attempts.

Affected VersionsENISA

anything-llm ≤ 1.11.1

Affected Packages

euvd anything_llm no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

AnythingLLM is a Large Language Model (LLM) context management application that allows users to convert content into contextual references for AI chatbots. The vulnerability exists in the getTableSchemaSql() method across all three database connector implementations (MySQL, PostgreSQL, and MSSQL), where table names are concatenated directly into SQL queries without proper parameterization or sanitization. This is a classic SQL injection vulnerability (CWE-89), where untrusted input flows directly into dynamically constructed SQL statements, allowing attackers to break out of the intended query structure and execute arbitrary SQL commands.

Know when MySQL 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

GitHub Advisory PRIMARY 7.7 HIGH
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector
Network
Attack Complexity
High
Attack Requirements
Present
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionGitHub Advisory

AnythingLLM is an application that turns pieces of content into context that any LLM can use as references during chatting. In 1.11.1 and earlier, a SQL injection vulnerability in the built-in SQL Agent plugin allows any user who can invoke the agent to execute arbitrary SQL commands on connected databases. The getTableSchemaSql() method in all three database connectors (MySQL, PostgreSQL, MSSQL) constructs SQL queries using direct string concatenation of the table_name parameter without sanitization or parameterization.

Executive ViewAI

Why It Matters

AnythingLLM versions 1.11.1 and earlier contain a critical SQL injection vulnerability in the SQL Agent plugin that allows any user with agent access to execute arbitrary commands against connected databases. This directly threatens data confidentiality, integrity, and availability for any organization using this application to interact with production databases.

Business Impact: Severe
Compensating Controls

Immediately disable the SQL Agent plugin feature; restrict database user accounts to read-only permissions with minimal table/schema access; implement network segmentation to limit which systems can reach connected databases; deploy WAF rules targeting SQL injection syntax patterns; enable comprehensive database query logging and alerting for suspicious commands; restrict AnythingLLM access to users who demonstrably require SQL Agent functionality only.

Threat Intelligence Overview

EPSS Score
0.0%
Top 92% exploitable
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
Very High

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Related Vulnerabilities in AnythingLLM Authentication Bypass and XSS

View all 3

More in MySQL

View all
CVE-2016-6662 CRITICAL POC
9.8 Sep 20

Oracle MySQL through 5.5.52, 5.6.x through 5.6.33, and 5.7.x through 5.7.15; MariaDB before 5.5.51, 10.0.x before 10.0.2

CVE-2012-5613 MEDIUM POC
6.0 Dec 03

MySQL 5.5.19 and possibly other versions, and MariaDB 5.5.28a and possibly other versions, when configured to assign the

CVE-2017-3599 HIGH POC
7.5 Apr 24

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Pluggable Auth). Rated high severity

CVE-2012-2122 MEDIUM POC
5.1 Jun 26

sql/password.c in Oracle MySQL 5.1.x before 5.1.63, 5.5.x before 5.5.24, and 5.6.x before 5.6.6, and MariaDB 5.1.x befor

CVE-2020-5398 HIGH
7.5 Jan 17

In Spring Framework, versions 5.2.x prior to 5.2.3, versions 5.1.x prior to 5.1.13, and versions 5.0.x prior to 5.0.16,

CVE-2012-5612 MEDIUM POC
6.5 Dec 03

Heap-based buffer overflow in Oracle MySQL 5.5.19 and other versions through 5.5.28, and MariaDB 5.5.28a and possibly ot

CVE-2012-5611 MEDIUM POC
6.5 Dec 03

Stack-based buffer overflow in the acl_get function in Oracle MySQL 5.5.19 and other versions through 5.5.28, and 5.1.53

CVE-2020-1967 HIGH POC
7.5 Apr 21

Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due

CVE-2016-6664 HIGH POC
7.0 Dec 13

mysqld_safe in Oracle MySQL through 5.5.51, 5.6.x through 5.6.32, and 5.7.x through 5.7.14; MariaDB; Percona Server befo

CVE-2015-3152 MEDIUM POC
5.9 May 16

Oracle MySQL before 5.7.3, Oracle MySQL Connector/C (aka libmysqlclient) before 6.1.3, and MariaDB before 5.5.44 use the

CVE-2026-24479 CRITICAL POC
9.8 Jan 27

HUSTOJ online judge has a path traversal vulnerability enabling arbitrary file access on the competition server.

CVE-2016-2105 HIGH
7.5 May 05

Integer overflow in the EVP_EncodeUpdate function in crypto/evp/encode.c in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy