# CVE-2026-54608: MythicalDash: Unauthenticated payment bypass in Stripe success-redirect endpoint allows arbitrary free credit top-up

> Attackers can bypass Stripe payment verification to grant themselves arbitrary free credits, causing financial loss for hosting providers.

- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-qmh4-5v7g-42jq

## What is CVE-2026-54608?

CVE-2026-54608 is a high-severity vulnerability in MythicalLTD MythicalDash, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization), CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-54608?


## How do I fix CVE-2026-54608?

No fix has been published for CVE-2026-54608 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-54608 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54608 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54608 and fix it if it is affected.

What it is: CVE-2026-54608 is a high-severity vulnerability in MythicalLTD MythicalDash, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54608 exists.

Affected product: MythicalLTD MythicalDash. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54608/ (Markdown: https://insights.sbomify.com/CVE-2026-54608/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54608
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54608
- OSV: https://osv.dev/vulnerability/CVE-2026-54608

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54608/
Summaries are generated and may contain mistakes; the official description above is the record.