Ghostfolio has a Stripe subscription bypass

Answer in brief

CVE-2026-47127 records a Medium severity (CVSS 6.5) vulnerability in Ghostfolio has a Stripe subscription bypass. The current sources do not mark it as known exploited. The current feed maps ghostfolio/ghostfolio (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 7, 2026Updated Sep 9, 2026Source checked Sep 22, 2026First seen by HOL Aug 7, 2026Material review Sep 9, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 6.5
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps ghostfolio/ghostfolio (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
ghostfolio/ghostfoliogeneric	< 3.4.0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for ghostfolio/ghostfolio.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Aug 7, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 9, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 7, 2026

Sources and claim methodology

Upstream source description

Ghostfolio is an open source wealth management software. Prior to version 3.4.0, Ghostfolio's Stripe checkout success-URL handler at `GET /api/v1/subscription/stripe/callback?checkoutSessionId=<id>` retrieves the Stripe Checkout Session by ID and unconditionally grants a Premium subscription to the session's `client_reference_id` — without ever checking `session.payment_status` or `session.status`. There is no separate Stripe webhook endpoint with `stripe-signature` verification; this callback is the sole code path that creates Stripe-driven subscriptions. Any authenticated user can self-grant a 1-year Premium subscription without ever paying. Version 3.4.0 rejects sessions unless `session.payment_status === 'paid'` AND `session.status === 'complete'` (fails closed). Additionally, new unique `stripeCheckoutSessionId` column → a session can't be redeemed twice (race-safe via DB unique constraint).

Quoted source text, attributed separately from HOL analysis.