Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-27621: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in TypiCMS Core

0
Medium
VulnerabilityCVE-2026-27621cvecve-2026-27621cwe-79
Published: Wed Feb 25 2026 (02/25/2026, 02:36:12 UTC)
Source: CVE Database V5
Vendor/Project: TypiCMS
Product: Core

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/04/2026, 19:05:30 UTC

Technical Analysis

TypiCMS Core, a multilingual CMS built on Laravel, contains a stored Cross-Site Scripting (XSS) vulnerability identified as CVE-2026-27621. This vulnerability exists in the file upload module for versions prior to 16.1.7. Users with file upload permissions can upload SVG files, which are validated only by MIME type but not sanitized for embedded scripts. SVG files can contain JavaScript, and an attacker can craft an SVG payload that executes malicious code when viewed by other users, such as administrators, leading to session hijacking or other client-side attacks. Additionally, a parsing bug causes a 500 error if the SVG lacks a viewBox attribute, but this does not prevent exploitation since attackers can add a valid viewBox attribute. The vulnerability requires no authentication to exploit beyond file upload permissions and no user interaction beyond viewing the file. The CVSS 4.0 vector indicates network attack vector, low attack complexity, no privileges required beyond upload rights, user interaction required (viewing), and high impact on confidentiality. The vulnerability is mitigated in version 16.1.7 of TypiCMS Core. No public exploits have been reported yet.

Potential Impact

This vulnerability allows attackers to execute arbitrary JavaScript in the context of the victim's browser, potentially leading to session hijacking, credential theft, or unauthorized actions performed with the victim's privileges. Since the vulnerability is stored XSS, it can persist and affect multiple users who access the malicious SVG file. Organizations using TypiCMS Core versions prior to 16.1.7 are at risk, especially if users with file upload permissions are untrusted or compromised. The impact is significant for administrative users who may have elevated privileges, increasing the risk of full system compromise. The vulnerability could also be used as a foothold for further attacks within the network or to spread malware. Although no known exploits are currently reported, the ease of exploitation and potential impact warrant prompt remediation.

Mitigation Recommendations

Organizations should immediately upgrade TypiCMS Core to version 16.1.7 or later, which contains the fix for this vulnerability. Until the upgrade is applied, restrict file upload permissions to trusted users only and implement additional server-side validation and sanitization of SVG file contents to remove any embedded scripts. Employ Content Security Policy (CSP) headers to limit the execution of inline scripts and restrict sources of executable code. Monitor logs for unusual file uploads and access patterns related to SVG files. Consider disabling SVG uploads if not required. Conduct regular security audits of user-uploaded content and educate users about the risks of uploading untrusted files. Additionally, implement web application firewalls (WAFs) with rules to detect and block malicious SVG payloads.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-20T22:02:30.026Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 699e6864b7ef31ef0bae9d1d

Added to database: 2/25/2026, 3:11:32 AM

Last enriched: 3/4/2026, 7:05:30 PM

Last updated: 4/10/2026, 8:00:14 PM

Views: 82

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses