CVE-2026-38948
Received Received - Intake
Cross-Site Scripting in FUEL CMS Asset Upload via SVG Files

Publication date: 2026-04-28

Last updated on: 2026-04-28

Assigner: MITRE

Description
Cross-Site Scripting (XSS) vulnerability exists in FUEL CMS v1.5.2 and before within the asset upload functionality. The application fails to properly sanitize uploaded SVG files, allowing a low-privileged authenticated user to upload a crafted SVG file containing malicious code.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-28
Last Modified
2026-04-28
Generated
2026-05-07
AI Q&A
2026-04-28
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
fuel_cms fuel_cms to 1.5.2 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-38948 is a Stored Cross-Site Scripting (XSS) vulnerability in FUEL CMS version 1.5.2 and earlier. It exists in the asset upload functionality where low-privileged authenticated users can upload malicious SVG files containing embedded JavaScript. These SVG files are not properly sanitized and are stored as-is. When an administrator opens or previews such a malicious SVG file, the embedded JavaScript executes within the administrator's browser session.

The executed script can extract sensitive information such as the administrator's CSRF token and use it to perform authenticated requests that modify critical account settings like username, email address, and password, leading to a full administrator account takeover.


How can this vulnerability impact me? :

This vulnerability can lead to a complete compromise of the FUEL CMS instance. An attacker with low privileges can upload a malicious SVG file that, when viewed by an administrator, executes JavaScript to steal the administrator's CSRF token and change administrator credentials.

As a result, the attacker gains full administrator access, allowing them to control the CMS, modify or delete content, change configurations, and potentially use the compromised system to launch further attacks.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by checking for the presence of malicious SVG files uploaded by low-privileged users in the /fuel/assets directory of the FUEL CMS installation.

One approach is to search for SVG files containing embedded JavaScript code, which is unusual and indicative of an exploit attempt.

Suggested commands to detect such files include using grep or similar tools to scan SVG files for script tags or JavaScript event handlers.

  • grep -r --include='*.svg' '<script' /path/to/fuel/assets
  • grep -r --include='*.svg' 'onload=' /path/to/fuel/assets
  • grep -r --include='*.svg' 'javascript:' /path/to/fuel/assets

Additionally, monitoring web server logs for unusual access patterns to SVG files or unexpected administrator actions after SVG file previews may help detect exploitation.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include restricting or disabling the upload of SVG files by low-privileged users to prevent malicious files from being uploaded.

If SVG uploads are necessary, implement proper sanitization of SVG files to remove any embedded JavaScript or potentially harmful content before storage.

Administrators should avoid opening or previewing SVG files uploaded by low-privileged users until the vulnerability is patched or mitigated.

Review and tighten user privileges to limit who can upload files and access sensitive areas of the CMS.

Monitor for suspicious activity, such as unexpected changes to administrator credentials, which may indicate exploitation.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability allows a low-privileged authenticated user to upload malicious SVG files that can lead to full administrator account takeover, resulting in a complete compromise of the CMS instance.

Such a compromise can lead to unauthorized access, modification, or disclosure of sensitive data managed by the CMS, which may violate data protection requirements under standards like GDPR and HIPAA.

Specifically, the exploitation impacts confidentiality, integrity, and availability of the system at a high level, increasing the risk of data breaches and unauthorized data processing.

Therefore, organizations using affected versions of FUEL CMS may face compliance risks if this vulnerability is exploited, as it undermines the security controls required by these regulations.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart