<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 09 Oct 2026 14:45:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-47127 — Ghostfolio has a Stripe subscription bypass</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-47127</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ghostfolio&lt;/p&gt;
&lt;p&gt;Ghostfolio is an open source wealth management software. Prior to version 3.4.0, Ghostfolio&amp;#39;s Stripe checkout success-URL handler at `GET /api/v1/subscription/stripe/callback?checkoutSessionId=&amp;lt;id&amp;gt;` retrieves the Stripe Checkout Session by ID and unconditionally grants a Premium subscription to the session&amp;#39;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 === &amp;#39;paid&amp;#39;` AND `session.status === &amp;#39;complete&amp;#39;` (fails closed). Additionally, new unique `stripeCheckoutSessionId` column → a session can&amp;#39;t be redeemed twice (race-safe via DB unique constraint).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ghostfolio&lt;/p&gt;
&lt;p&gt;Ghostfolio is an open source wealth management software. Prior to version 3.4.0, Ghostfolio&amp;#39;s Stripe checkout success-URL handler at `GET /api/v1/subscription/stripe/callback?checkoutSessionId=&amp;lt;id&amp;gt;` retrieves the Stripe Checkout Session by ID and unconditionally grants a Premium subscription to the session&amp;#39;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 === &amp;#39;paid&amp;#39;` AND `session.status === &amp;#39;complete&amp;#39;` (fails closed). Additionally, new unique `stripeCheckoutSessionId` column → a session can&amp;#39;t be redeemed twice (race-safe via DB unique constraint).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-47127</guid>
    </item>
  </channel>
</rss>
