CVE-2026-115329 — Lotus through 0.10.2 Cross-Organization IDOR via SubscriptionViewSet
Lotus through 0.10.2 contains an insecure direct object reference vulnerability in SubscriptionViewSet.get_object() that uses an unscoped queryset without organization filtering or permission checks. Authenticated users or API keys from any organization can supply another organization's subscription_id to read, cancel, update, switch plans, or modify addons, altering another tenant's billing.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.3% (30-day exploitation probability)+3
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Uselotus Lotus).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 6.0 | CVSS 4.0 | Medium | — | — | disclosure@vulncheck.com via NIST National Vulnerability Database |
| 6.0 | CVSS 4.0 | Medium | — | — | VulnCheck via CVE Program (cve.org) e CISA ADP |
| 5.9 | CVSS 3.1 | Medium | 1.6 | 4.2 | disclosure@vulncheck.com via NIST National Vulnerability Database |
| 5.9 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
| 5.9 | CVSS 3.1 | Medium | — | — | VulnCheck via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N (score shown at the top: disclosure@vulncheck.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CWE-639 · Authorization Bypass Through User-Controlled Key (IDOR)
EPSS over time FIRST
Oct 23, 2026 → Oct 27, 2026 · 5 reading(s) · max 0.26%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Audit administrative actions and access to resources outside each user’s normal pattern.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Source status changed · Received → Deferred
- Affected products added · uselotus/lotus
- Record published
- CVSS changed · 5.9
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 22, 2026 – Oct 23, 2026
- 1× Official description updated · Oct 22, 2026 – Oct 22, 2026
References
8 on the record
- github.com/uselotus/lotus/commit/1375d5140795d72251c89f47200879b9bd1d6d96
- github.com/uselotus/lotus/pull/802
- github.com/uselotus/lotus/blob/0.10.2/backend/api/views.py
- github.com/uselotus/lotus/issues/799
- www.vulncheck.com/advisories/lotus-through-0.10.2-cross-organization-idor-via-subscript
- github.com/uselotus/lotus
- nvd.nist.gov/vuln/detail/CVE-2026-115329
- github.com/advisories/GHSA-pjmr-f3w6-46qx
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-115330 Lotus through 0.10.2 SQL Injection via Custom SQL Billable Metrics 6d
- High CVE-2026-115331 Lotus through 0.10.2 SQL Injection via Metric Property Names and Filters 6d
- High CVE-2026-115332 Lotus through 0.10.2 SQL Injection via Subscription Filter Keys 6d
- Medium CVE-2026-115333 Lotus through 0.10.2 Improper Authentication via Event Ingestion API Key Prefix 6d
- Medium CVE-2026-115334 Lotus through 0.10.2 Authorization Bypass via switch_organization Endpoint 6d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-115329 is "Lotus through 0.10.2 Cross-Organization IDOR via SubscriptionViewSet", rated Medium. It affects Lotus (Uselotus); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.9 describes technical severity. EPSS 0.26% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.