CVE-2025-46335: Mobile Security Framework (MobSF) Allows Stored Cross Site Scripting (XSS) via malicious SVG Icon Upload
First published: Mon May 05 2025(Updated: )
**Vulnerable MobSF Versions:** <= v4.3.2 **CVSS V4.0 Score:** 8.6 (CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N) **Details:** A Stored Cross-Site Scripting (XSS) vulnerability has been identified in MobSF versions ≤ 4.3.2. The vulnerability arises from improper sanitization of user-supplied SVG files during the Android APK analysis workflow. When an Android Studio project contains a malicious SVG file as an app icon (e.g path, /app/src/main/res/mipmap-hdpi/ic_launcher.svg), and the project is zipped and uploaded to MobSF, the tool processes and extracts the contents without validating or sanitizing the SVG. Upcon ZIP extraction this icon file is saved by MobSF to: user/.MobSF/downloads/<filename>.svg This file becomes publicly accessible via the web interface at: http://127.0.0.1:8081/download/filename.svg If the SVG contains embedded JavaScript (e.g., an XSS payload), accessing this URL via a browser leads to the execution of the script in the context of the MobSF user session, resulting in stored XSS. **Proof Of Concept:** 1. Create a malicious SVG file (ic_launcher.svg) with an embedded XSS payload.  2. Place the file in the Android Studio project directory: /app/src/main/res/mipmap-hdpi/ic_launcher.svg  3. Zip the project directory and upload it to MobSF.  4. After the scan, navigate to the "Recent Scans" page in the MobSF web interface and click on the scan entry and open the icon file in a new browser tab.  5. The XSS payload is executed, confirming the vulnerability. 
Credit: security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| pip/mobsf | <=4.3.2 | 4.3.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://github.com/MobSF/Mobile-Security-Framework-MobSF/security/advisories/GHSA-mwfg-948f-2cc5
- https://github.com/MobSF/Mobile-Security-Framework-MobSF/commit/6987a946485a795f4fd38cebdb4860b368a1995d
- https://nvd.nist.gov/vuln/detail/CVE-2025-46335
- https://github.com/advisories/GHSA-mwfg-948f-2cc5 (Advisory)
Frequently Asked Questions
What is the severity of CVE-2025-46335?
CVE-2025-46335 has a CVSS v4.0 score of 8.6, indicating it is a high severity vulnerability.
How do I fix CVE-2025-46335?
To fix CVE-2025-46335, upgrade MobSF to version 4.3.3 or later.
What type of vulnerability is CVE-2025-46335?
CVE-2025-46335 is a Stored Cross-Site Scripting (XSS) vulnerability.
Which versions of MobSF are affected by CVE-2025-46335?
CVE-2025-46335 affects MobSF versions 4.3.2 and earlier.
What causes the CVE-2025-46335 vulnerability?
The CVE-2025-46335 vulnerability is caused by improper sanitization of user input.
- agent/weakness
- agent/softwarecombine
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- agent/title
- agent/type
- agent/description
- agent/author
- agent/severity
- agent/event
- collector/nvd-api
- source/NVD
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-mwfg-948f-2cc5
- alias/CVE-2025-46335
- agent/software-canonical-lookup
- agent/last-modified-date
- agent/references
- collector/nvd-cve
- collector/epss-latest
- source/FIRST
- agent/source
- agent/tags
- agent/epss
- package-manager/pip