typicms/core
Affected
- introduced
16.0.0, fixed16.1.7(ecosystem)
Fixed versions
16.1.7
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-27621
TypiCMS Core has Stored Cross-Site Scripting (XSS) via SVG File Upload
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
TypiCMS\Modules\Core\Http\Requests\FileFormRequest.php and TypiCMS\Modules\Core\Services\FileUploader.php.The vulnerability stems from two main points:
FileFormRequest explicitly whitelists svg as an allowed MIME type for uploads.FileUploader service saves the SVG file to the server without parsing and sanitizing its content to remove potentially malicious elements like <script> tags or on* event handlers.When the default filesystem disk is set to public, the uploaded SVG file is stored in a publicly accessible directory, making it trivial to access the file via a direct URL and trigger the XSS payload.
III. Proof of Concept (PoC)
malicious.svg with the following content. The viewBox attribute is included to bypass the application's parsing bug. ```xml
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 100 100">
<script>
// A simple PoC to demonstrate the vulnerability
alert('XSS in TypiCMS! Your session cookie is: ' + document.cookie);
</script>
<text x="10" y="50">If you see this, the script has run.</text>
</svg>
```
/admin/files). * Upload the malicious.svg file. The application will accept the file and store it.<img width="2540" height="1217" alt="image" src="https://github.com/user-attachments/assets/beb8ace9-ac39-442c-a2bc-3fbfb09f8c32" />
<img width="1718" height="671" alt="image" src="https://github.com/user-attachments/assets/9cd4a3f8-28e3-4223-8203-7ab292eaf95f" />
http://<your-site>/storage/files/malicious.svg. * Anyone who navigates to this URL will have the embedded JavaScript executed in their browser. * An attacker can send this link to a privileged user (e.g., an administrator). When the administrator clicks the link, their session cookies can be stolen, or the attacker can perform actions on their behalf.<img width="2091" height="704" alt="image" src="https://github.com/user-attachments/assets/99c915bb-a518-46aa-b237-390cd58f34e7" />
<img width="1457" height="996" alt="image" src="https://github.com/user-attachments/assets/0ed000ec-78cf-4ed8-8cd5-2886fbb2afc0" />
IV. Impact
Successful exploitation of this vulnerability allows an attacker to execute arbitrary JavaScript in the context of the victim's browser. Although the use of the HttpOnly flag on session cookies prevents direct theft of the session ID via document.cookie, the attacker can still achieve a full compromise of the victim's account by performing actions on their behalf.
The impact includes:
Because the attacker can perform any action as an authenticated administrator, this vulnerability effectively leads to a full application compromise, even without direct access to the session cookie. The risk is High.
V. Recommended Patches and Mitigations
It is recommended to apply a defense-in-depth approach to mitigate this vulnerability.
<script>, <style>, <foreignObject> tags, and all on* event attributes. This can be achieved using a dedicated SVG sanitization library.'svg' from the list of allowed MIME types in TypiCMS\Modules\Core\Http\Requests\FileFormRequest.php. ```php
// In FileFormRequest.php
// BEFORE:
$fileRule = 'mimes:jpeg,gif,png,...,svg,...|max:...';
// AFTER:
$fileRule = 'mimes:jpeg,gif,png,...,pdf,...|max:...'; // Removed 'svg'
```
Medium Basis: The source's own band: MODERATE
16.0.0, fixed 16.1.7 (ecosystem)16.1.7
The export has no generic command for this ecosystem.
15.0.0, fixed 15.0.29 (ecosystem)15.0.29
The export has no generic command for this ecosystem.
14.0.0, fixed 14.0.27 (ecosystem)14.0.27
The export has no generic command for this ecosystem.
13.0.0, fixed 13.0.9 (ecosystem)13.0.9
The export has no generic command for this ecosystem.
0, fixed 12.0.5 (ecosystem)12.0.5
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0