Skip to main content
Vulnerability Database/CVE-2026-115330

CVE-2026-115330: Lotus SQL Injection Vulnerability

CVE-2026-115330 is an SQL injection flaw in Lotus through version 0.10.2 that enables authenticated users to execute arbitrary SQL commands via stacked queries, potentially accessing or modifying data across all tenants. This article covers technical details, affected versions, impact analysis, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-115330 Overview

CVE-2026-115330 is a SQL injection vulnerability [CWE-89] affecting Lotus through version 0.10.2, an open-source pricing and billing platform. Authenticated organization users can append stacked SQL statements to custom billable metric queries submitted via POST /app/metrics/. The application validates only the first statement, allowing semicolon-separated SQL to execute against the backend database. Exploitation enables cross-tenant data access, letting an attacker read or modify records belonging to any organization in the deployment. The flaw undermines multi-tenant isolation guarantees in affected Lotus deployments.

Critical Impact

Authenticated tenants can bypass first-statement validation, execute arbitrary SQL via stacked queries, and read or modify data across all tenants in a shared Lotus deployment.

Affected Products

  • Lotus (uselotus/lotus) through version 0.10.2
  • Lotus metering_billing custom billable metrics component
  • Lotus POST /app/metrics/ endpoint

Discovery Timeline

  • 2026-10-22 - CVE-2026-115330 published to the National Vulnerability Database (NVD)
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-115330

Vulnerability Analysis

Lotus allows organization administrators to define custom billable metrics backed by user-supplied SQL. The server validates these queries by inspecting only the first SQL statement submitted. Because the underlying database driver executes stacked statements separated by semicolons, additional statements appended after the validated query run without inspection. An authenticated user with permission to create metrics can therefore submit a benign-looking SELECT followed by arbitrary INSERT, UPDATE, DELETE, or SELECT statements. The injected SQL executes with the application's database privileges, which span all tenants in the shared schema. This breaks tenant isolation and enables both confidentiality and integrity compromise across the deployment.

Root Cause

The root cause is incomplete input validation in the custom billable metrics handler. The code path referenced in backend/metering_billing/aggregation/billable_metrics.py parses and validates only the first SQL statement from the submitted payload before passing the full string to the database executor. Because validation does not reject or strip stacked statements, the first-statement check is trivially bypassed by appending ; and additional SQL.

Attack Vector

Exploitation requires an authenticated organization-level account and network access to the Lotus API. The attacker issues a POST /app/metrics/ request containing a custom SQL metric definition whose query body appends stacked statements after a valid leading SELECT. The backend validates the first statement, forwards the complete payload to the database, and executes every statement in sequence. No user interaction is required beyond the attacker's authenticated session.

For technical details, refer to the VulnCheck SQL Injection Advisory and the vulnerable code reference in the Lotus repository.

Detection Methods for CVE-2026-115330

Indicators of Compromise

  • POST /app/metrics/ requests whose JSON body contains SQL payloads with multiple semicolon-separated statements.
  • Custom metric definitions referencing tables or schemas outside the submitting organization's tenant scope.
  • Database audit entries showing INSERT, UPDATE, or DELETE statements originating from the metrics aggregation worker when none are expected.
  • Unexpected changes to tenant records, billing data, or user accounts without a corresponding administrative action.

Detection Strategies

  • Inspect application and reverse-proxy logs for /app/metrics/ POST bodies containing ; followed by additional SQL keywords such as SELECT, UPDATE, DROP, or UNION.
  • Enable database query logging and alert on multi-statement executions originating from the Lotus application user.
  • Correlate metric creation events with subsequent cross-tenant row access in audit logs.

Monitoring Recommendations

  • Baseline the normal volume and shape of custom metric SQL and alert on statements that touch sensitive tables such as auth_user, organization, or billing records.
  • Monitor for authenticated users creating metrics referencing schemas outside their own tenant identifier.
  • Forward Lotus application logs and PostgreSQL audit logs to a centralized analytics platform for retention and correlation.

How to Mitigate CVE-2026-115330

Immediate Actions Required

  • Restrict access to the POST /app/metrics/ endpoint to trusted administrator accounts until a patched release is deployed.
  • Audit all existing custom billable metrics for stacked statements or references to tables outside the owning tenant.
  • Rotate database and API credentials if evidence of exploitation is found, and review tenant data for unauthorized modifications.

Patch Information

At the time of publication, the advisory identifies Lotus versions through 0.10.2 as affected. Monitor the Lotus project repository and the VulnCheck advisory for a fixed release and upgrade guidance. Deployments should plan to upgrade as soon as a patched version is available.

Workarounds

  • Configure the database driver or connection string to disable multi-statement execution where supported (for example, by rejecting stacked queries at the driver layer).
  • Run the Lotus application under a database role with per-tenant row-level security or restricted DML privileges to limit the blast radius of injected SQL.
  • Place a web application firewall rule in front of /app/metrics/ that blocks request bodies containing semicolon-separated SQL statements.
  • Temporarily disable the custom SQL billable metric feature in environments where it is not required.
bash
# Example WAF-style pattern to flag stacked SQL in metric submissions
# (adapt to your WAF or reverse proxy syntax)
location /app/metrics/ {
    if ($request_method = POST) {
        if ($request_body ~* ";\s*(select|insert|update|delete|drop|alter|union)\b") {
            return 403;
        }
    }
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.