CVE-2026-108100
Deferred Deferred - Pending Action

BaseFortify

Publication date: 2026-10-09

Last updated on: 2026-10-09

Assigner: VulnCheck

Description
HortusFox (hortusfox-web) before 6.2 contains an SQL injection vulnerability that allows API token holders to inject SQL by supplying crafted include_info values to the /api/locations/list endpoint. Attackers can place subqueries in include_info, which PlantsModel::getSpecificInfo() concatenates into the column list, to read any database table including user password hashes.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

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

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
danielbrendel hortusfox-web 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 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.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

HortusFox before version 6.2 has an SQL injection flaw in its API. API token holders can inject malicious SQL by providing specially crafted include_info values to the /api/locations/list endpoint. The application concatenates these values into database queries, allowing attackers to read any table including sensitive user password hashes.

Detection Guidance

To detect this SQL injection vulnerability in HortusFox, monitor API requests to the /api/locations/list endpoint for crafted include_info parameters containing SQL subqueries. Check server logs for unusual database queries or errors related to PlantsModel::getSpecificInfo().

Impact Analysis

If you use HortusFox with API token access, an attacker with a token could exploit this to steal database contents like user passwords. This could lead to unauthorized access to accounts, data breaches, or further attacks on your systems.

Compliance Impact

This vulnerability could lead to unauthorized data access, violating GDPR's data protection requirements and HIPAA's safeguards for protected health information. Organizations may face fines or penalties for failing to protect sensitive data due to this flaw.

Mitigation Strategies

Immediately update HortusFox to version 6.2 or later. If an update is not possible, restrict API token access to trusted users only and implement input validation for include_info parameters to block SQL subqueries.

Chat Assistant

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

EPSS Chart