# CVE-2026-115332: Lotus SQL injection in subscription filter key validation

Source: https://junglewise.ai/threats/cve-2026-115332-lotus-through-0-10-2-contains-an-sql-injection-vulnerability  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-22. Updated: 2026-10-22  
License: CC BY 4.0 with a link back

CVE-2026-115332 · Severity: high · CVSS 8.8 · Published 2026-10-22

Lotus is an open-source pricing and billing infrastructure platform. An authenticated user within an organization can inject malicious SQL code when registering subscription filter keys, which are then rendered without proper escaping in database aggregation queries. This allows attackers to manipulate billing data or access sensitive information in the shared database.

Technologies: [Uselotus Lotus](https://junglewise.ai/threats/technologies/lotus). Vendors: [Uselotus](https://junglewise.ai/threats/vendors/uselotus).

## Quick answers

**Is CVE-2026-115332 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-115332 being exploited in the wild.

**How severe is CVE-2026-115332?** High severity, with a CVSS score of 8.8, published 22 October 2026.

**Which products and versions are affected?** Uselotus Lotus through 0.10.2.

**Is there a fix for CVE-2026-115332?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-115332 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-115332?** Check whether you run Uselotus Lotus at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability exists in subscription filter key validation in Lotus through 0.10.2, where crafted subscription_filter_keys bypass keyword-only validation and are rendered as unquoted group-by identifiers in SQL usage aggregation queries. An authenticated organization user can exploit this to inject arbitrary SQL into multi-tenant database queries. The issue stems from insufficient input sanitization in the model serializers prior to SQL query construction.

## Affected products

- uselotus Lotus through 0.10.2

## Timeline

- 2026-10-22: disclosed

## References

- [https://github.com/uselotus/lotus](https://github.com/uselotus/lotus)
- [https://github.com/uselotus/lotus/blob/0.10.2/backend/metering_billing/serializers/model_serializers.py](https://github.com/uselotus/lotus/blob/0.10.2/backend/metering_billing/serializers/model_serializers.py)

## Related threats

- [Lotus improper authentication in event ingestion middleware](https://junglewise.ai/threats/cve-2026-115333-lotus-through-0-10-2-contains-an-improper-authentication)
- [Lotus SQL injection in custom metric queries](https://junglewise.ai/threats/cve-2026-115330-lotus-through-0-10-2-contains-an-sql-injection-vulnerability)