{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54608 exists.","fix":"No fix has been published for CVE-2026-54608 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-54608 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54608 exists.\n\nAffected product: MythicalLTD MythicalDash. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54608/ (Markdown: https://insights.sbomify.com/CVE-2026-54608/index.md)","id":"CVE-2026-54608","markdown":"https://insights.sbomify.com/CVE-2026-54608/index.md","name":"CVE-2026-54608","record":{"aliases":["GHSA-qmh4-5v7g-42jq"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Pterodactyl client area","requires_auth":"low_privilege","summary":"Attackers can bypass Stripe payment verification to grant themselves arbitrary free credits, causing financial loss for hosting providers.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"MythicalDash: Unauthenticated payment bypass in Stripe success-redirect endpoint allows arbitrary free credit top-up","id":"CVE-2026-54608","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"QTINeon has unauthenticated relay-to-host amplification via unbounded RECONNECT_REQUEST forwarding","id":"CVE-2026-54609"},"packages":[],"prev":{"headline":"FastGPT: SSRF in HTTP-tool OpenAPI schema importer via SwaggerParser $ref (bypasses the isInternalAddress guard)","id":"CVE-2026-54607"},"products":["MythicalDash"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-18","vendors":["MythicalLTD"]},"summary":"Attackers can bypass Stripe payment verification to grant themselves arbitrary free credits, causing financial loss for hosting providers.","url":"https://insights.sbomify.com/CVE-2026-54608/"}