Advisory record · GHSA-xfvg-8v67-j7wp

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

CVSS 6.8 MediumEPSS 0.0022 · 13th percentile

Published by the GitHub Advisory Database at 25 Feb 2026, 16:06 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
typicms/corePackagist>=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.516.1.7, 15.0.29, 14.0.27, 13.0.9, 12.0.5
Identifiers
GHSA-xfvg-8v67-j7wp · CVE-2026-27621 · PKSA-4g4t-fqh1-f8mt
Weakness (CWE)
CWE-79
Published
25 Feb 2026
Updated
9 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

TypiCMS Core versions below 12.0.5, from 13.0.0 before 13.0.9, from 14.0.0 before 14.0.27, from 15.0.0 before 15.0.29, and from 16.0.0 before 16.1.7 are affected. A user with file upload permission can upload an SVG containing script, and when another user such as an administrator opens the file, the script runs in their browser and can perform actions as that user. Upgrade to 12.0.5, 13.0.9, 14.0.27, 15.0.29, or 16.1.7 as appropriate for your version. Where upgrading is not possible, the source suggests disabling SVG uploads by removing svg from the allowed MIME types.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.8 Medium 4.0 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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0022, the 13th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:25 UTC First seen by agentprime
  2. 31 Oct 2026, 14:25 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.