MobSF Mobile-Security-Framework-MobSF 4.3.0 dynamic_analysis.html CFBundleIdentifier cross site scripting

Summaryinfo

A vulnerability identified as problematic has been detected in MobSF Mobile-Security-Framework-MobSF 4.3.0. Affected by this issue is some unknown functionality of the file dynamic_analysis.html. The manipulation of the argument CFBundleIdentifier leads to cross site scripting. This vulnerability is traded as CVE-2025-24803. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in MobSF Mobile-Security-Framework-MobSF 4.3.0. This issue affects some unknown functionality of the file dynamic_analysis.html. The manipulation of the argument CFBundleIdentifier with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to 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. Impacted is integrity. The summary by CVE is:

Mobile Security Framework (MobSF) is an automated, all-in-one mobile application (Android/iOS/Windows) pen-testing, malware analysis and security assessment framework. According to Apple's documentation for bundle ID's, it must contain only alphanumeric characters (A–Z, a–z, and 0–9), hyphens (-), and periods (.). However, an attacker can manually modify this value in the `Info.plist` file and add special characters to the `CFBundleIdentifier` value. The `dynamic_analysis.html` file does not sanitize the received bundle value from Corellium and as a result, it is possible to break the HTML context and achieve Stored XSS. This issue has been addressed in version 4.3.1 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2025-24803 since 01/23/2025. The exploitation is known to be easy. The attack may be initiated remotely. Additional levels of successful authentication are needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.

By approaching the search of inurl:dynamic_analysis.html it is possible to find vulnerable targets with Google Hacking.

Upgrading to version 4.3.1 eliminates this vulnerability. Applying the patch 05206e72cae35b311615a70e51e1a946955c5e83 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• MobSF

Name

• Mobile-Security-Framework-MobSF

Version

• 4.3.0

License

• open-source

Website

• Product: https://github.com/MobSF/Mobile-Security-Framework-MobSF/

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion