Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.8

TypiCMS Core has Stored Cross-Site Scripting (XSS) via SVG File Upload

CVE-2026-27621GHSA-xfvg-8v67-j7wp

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (typicms/core 16.1.7, 15.0.29, 14.0.27, 13.0.9, 12.0.5), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist typicms/core

    Affected
    >= 16.0.0, < 16.1.7>= 15.0.0, < 15.0.29>= 14.0.0, < 14.0.27>= 13.0.0, < 13.0.9< 12.0.5
    Fixed in
    14.0.27, 13.0.9, 16.1.7, 12.0.5, 15.0.29

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.8 · 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 · score source
EPSS
  • CVE-2026-27621: 0.22% estimated exploitation activity in the next 30 days; percentile 13.05 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

I. Summary A Stored Cross-Site Scripting (XSS) vulnerability exists in the file upload module of TypiCMS. 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. II. Vulnerability Details Vulnerability Type: Stored Cross-Site Scripting (XSS) (CWE-79) Affected Component: TypiCMS\Modules\Core\Http\Requests\FileFormRequest.php…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-xfvg-8v67-j7wp

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-27621

Advisory: TypiCMS Core has Stored Cross-Site Scripting (XSS) via SVG File Upload
IDs: CVE-2026-27621, GHSA-xfvg-8v67-j7wp
Record: https://patchnext.com/advisories/cve-2026-27621 (revision 1, source checked 26 Oct 2026, 14:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: typicms/core 16.1.7, 15.0.29, 14.0.27, 13.0.9, 12.0.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typicms/core: affected >= 16.0.0, < 16.1.7; >= 15.0.0, < 15.0.29; >= 14.0.0, < 14.0.27; >= 13.0.0, < 13.0.9; < 12.0.5; fixed in 14.0.27, 13.0.9, 16.1.7, 12.0.5, 15.0.29

## Suggested inspection (read-only)
- Packagist typicms/core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on typicms/core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xfvg-8v67-j7wp (GitHub-reviewed advisory GHSA-xfvg-8v67-j7wp lists affected ranges: Packagist typicms/core >=16.0.0 =15.0.0 =14.0.0 =13.0.0 =0 <12.0.5)

Commands are suggestions: review each one before running it.

Loading voting…