CVE-2026-38626
Received Received - Intake

SQL Injection in Garlic-Hub

Vulnerability report for CVE-2026-38626, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-10

Last updated on: 2026-09-10

Assigner: MITRE

Description

Garlic-Hub v1.0.1 is vulnerable to SQL Injection in src/Modules/Items/Repositories/ItemsRepository.php.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-10
Last Modified
2026-09-10
Generated
2026-09-10
AI Q&A
2026-09-10
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
garlic-hub garlic-hub 1.0.1

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a critical SQL Injection (SQLi) vulnerability in Garlic-Hub v1.0.1, a digital signage management system. The flaw allows attackers to bypass security layers and interact directly with the database engine due to improper string concatenation in the $owner variable within a SELECT query in ItemsRepository.php.

Detection Guidance

To detect this SQL Injection vulnerability in Garlic-Hub v1.0.1, check if the application uses the vulnerable ItemsRepository.php file. Look for raw SQL queries with string concatenation in the $owner variable. You can test for SQLi by sending payloads like ' OR 1=1 -- and observing server delays or errors.

Impact Analysis

Attackers could exploit this to execute malicious SQL commands, leading to full data exfiltration, bypassing authentication, or even remote code execution if the database user has FILE privileges. A proof-of-concept attack caused a 5-second server delay, confirming full query control.

Compliance Impact

This vulnerability could lead to unauthorized data access or exfiltration, violating GDPR's data protection requirements and HIPAA's safeguards for protected health information. Non-compliance risks include legal penalties and reputational damage.

Mitigation Strategies

Immediately update Garlic-Hub to the latest patched version. If no patch exists, modify ItemsRepository.php to use PDO Prepared Statements instead of raw SQL concatenation. Ensure database user permissions are restricted to prevent file access or code execution.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-38626. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart