---
id: CVE-2026-54608
title: MythicalDash is a Pterodactyl client area
summary: >-
  MythicalDash is a Pterodactyl client area. In 3.5.4-aurora and earlier, GET
  /api/stripe/process in backend/app/Api/System/Gateways/Stripe.php creates a
  pending row in mythicaldash_stripe_payments before Stripe checkout succeeds
  and embed…
severity: high
cvss: 7.1
cvssVector: 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N'
cwe:
  - CWE-345
  - CWE-862
vendor: MythicalLTD
product: MythicalDash
affected:
  - MythicalDash <= 3.5.4-aurora
published: '2026-09-17'
updated: '2026-09-23'
sourceUpdated: '2026-09-23T19:43:31.933'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-54608'
references:
  - url: >-
      https://github.com/MythicalLTD/MythicalDash/commit/188d4c4ed80b8d364b0c4605a9e38ceaab746e39
    label: security-advisories@github.com
  - url: >-
      https://github.com/MythicalLTD/MythicalDash/security/advisories/GHSA-qmh4-5v7g-42jq
    label: security-advisories@github.com
  - url: >-
      https://github.com/MythicalLTD/MythicalDash/security/advisories/GHSA-qmh4-5v7g-42jq
    label: 134c704f-9b21-4f2e-91b3-4a467353bcc0
tags:
  - nvd
  - cve.org
  - exploit-available
epss: 0.00201
epssPercentile: 0.09003
exploitAvailable: true
ssvc:
  exploitation: poc
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-09-18T13:12:03.233236Z'
cvssSource: cna
ingestedAt: '2026-09-17T22:30:21.401Z'
---

## Overview

MythicalDash is a Pterodactyl client area. In 3.5.4-aurora and earlier, GET /api/stripe/process in backend/app/Api/System/Gateways/Stripe.php creates a pending row in mythicaldash_stripe_payments before Stripe checkout succeeds and embeds the payment code in the success redirect, while GET /api/stripe/processed accepts that code without constructing a Session, checking ownership, or retrieving the Stripe Checkout Session to require payment_status to be paid and amount_total to match the expected charge. An ordinary authenticated user can request an attacker-selected coins amount, abandon or fail payment, and submit the pending code directly to the unauthenticated processed endpoint. StripeDB::isPending() then permits User::addCreditsAtomic() to grant the unpaid amount and mark the row processed even though Stripe has not confirmed payment. This permits arbitrary free virtual-currency top-ups and direct financial loss through consumption of hosting resources. No fixed version is available as of this review.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.