CVE-2026-119548

Lago through 1.55.0 Cross-Organization Invoice Payment Manipulation via Stripe Webhook

Published Oct 30, 2026 CVSS 4.0 · 2.3 Low EPSS < 1% KEV · Not listed
Description
Lago through 1.55.0 contains an authorization bypass vulnerability in Invoices::Payments::StripeService that allows users of one organization to mark another organization's invoice as paid due to an unscoped invoice lookup. Attackers controlling their organization's Stripe integration can sign a payment_intent.succeeded event carrying a victim invoice UUID to unlock wallet top-ups or payment-gated subscriptions.

Analysis

AI-generated

Technical impact

The vulnerability in Lago version 1.55.0 allows a user of one organization to mark a different organization’s invoice as paid because the invoice lookup is not scoped to the requesting organization. An attacker who controls their own organization‘s Stripe integration can sign a payment_intent.succeeded event containing the victim invoice’s UUID, which triggers wallet top‑ups or activates payment‑gated subscriptions for the victim. This flaw constitutes an authorization bypass (CWE‑639) that can lead to financial loss and unintended service usage.

Affected Systems

The affected product is Lago from getlago, specifically all releases up to and including 1.55.0. Users of any 1.55.0 or earlier edition are vulnerable.

Risk and Exploitability

The published CVSS score of 2.3 indicates a low severity rating, and the vulnerability is not listed in CISA’s KEV catalog. Based on the description, the likely attack vector requires that the attacker controls the Stripe integration for their own organization to sign a valid webhook payload. Thus, the exploitability is limited to individuals with access to the secret signing key and the ability to craft a payment_intent.succeeded event. Remote or unauthenticated exploitation is therefore improbable. Nonetheless, the ability to misrepresent invoice ownership can lead to unauthorized payments or service activation for the victim organization.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Lago to a version newer than 1.55.0 that correctly scopes invoice lookup to the organization that initiates the payment.
  • Ensure that the Stripe webhook endpoint validates events by checking that the invoice UUID in a payment_intent.succeeded event belongs to the organization authorized to receive the payment, and reject any cross‑organization IDs.
  • Restrict access to the Stripe integration credentials so that only trusted services can sign webhook events, and rotate the secret keys regularly to minimize the risk of unauthorized event generation.

Generated by OpenCVE AI on October 30, 2026 at 13:07 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Getlago
Getlago lago
Vendors & Products Getlago
Getlago lago
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Lago through 1.55.0 contains an authorization bypass vulnerability in Invoices::Payments::StripeService that allows users of one organization to mark another organization's invoice as paid due to an unscoped invoice lookup. Attackers controlling their organization's Stripe integration can sign a payment_intent.succeeded event carrying a victim invoice UUID to unlock wallet top-ups or payment-gated subscriptions.
Title Lago through 1.55.0 Cross-Organization Invoice Payment Manipulation via Stripe Webhook
Weaknesses CWE-639
References
Metrics cvssV3_1

{'score': 3.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N'}

cvssV4_0

{'score': 2.3, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 30, 2026, 3:54 PM
Reserved
Oct 30, 2026, 10:53 AM
Status
Deferred
Published
Oct 30, 2026, 12:16 PM
Modified
Oct 30, 2026, 7:23 PM