CVE Catalog

CVE-2026-54608

HighCVSS 7.1
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.20%

9th percentile - higher than 9% of all known CVEs

Summary

In MythicalDash 3.5.4-aurora and earlier, the GET /api/stripe/processed endpoint accepts a payment code without constructing a Stripe Session, checking ownership, or verifying payment status. An authenticated user can abandon payment and submit the pending code to receive free virtual currency.

Risk Assessment

An attacker can perform arbitrary free virtual-currency top-ups, causing direct financial loss through consumption of hosting resources. No fixed version is available.

Recommendation

No fixed version is available — consider disabling or restricting the /api/stripe/processed endpoint and manually verifying Stripe payments. Monitor for unusual account top-ups.

Related vulnerabilities

Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS