Skip to main content

CVE-2025-9677: Improper Export of Android Application Components in Modo Legend of the Phoenix

Medium
VulnerabilityCVE-2025-9677cvecve-2025-9677
Published: Fri Aug 29 2025 (08/29/2025, 21:02:07 UTC)
Source: CVE Database V5
Vendor/Project: Modo
Product: Legend of the Phoenix

Description

A security flaw has been discovered in Modo Legend of the Phoenix up to 1.0.5. The affected element is an unknown function of the file AndroidManifest.xml of the component com.duige.hzw.multilingual. The manipulation results in improper export of android application components. The attack needs to be approached locally. The exploit has been released to the public and may be exploited. The vendor was contacted early about this disclosure but did not respond in any way.

AI-Powered Analysis

AILast updated: 08/29/2025, 21:32:46 UTC

Technical Analysis

CVE-2025-9677 is a medium-severity vulnerability affecting the Android application 'Modo Legend of the Phoenix' versions 1.0.0 through 1.0.5. The flaw arises from improper exportation of Android application components defined in the AndroidManifest.xml file, specifically related to the component com.duige.hzw.multilingual. Improper export means that certain application components, such as activities, services, or broadcast receivers, are unintentionally made accessible to other applications or processes on the device. This can lead to unauthorized access or manipulation of these components. The vulnerability requires local access to the device, meaning an attacker must have some level of access to the device environment (e.g., physical access or a malicious app installed on the device). No user interaction is required once local access is achieved, and the attack complexity is low. The CVSS v4.0 score is 4.8, reflecting a medium severity with local attack vector, low attack complexity, no privileges required beyond local access, and no user interaction needed. The impact on confidentiality, integrity, and availability is limited but present, as improper export could allow unauthorized data access or manipulation within the app's components. The vendor was notified but did not respond, and no patches are currently available. The exploit code has been publicly released, increasing the risk of exploitation, although no known exploits in the wild have been reported yet. This vulnerability highlights the importance of correctly configuring AndroidManifest.xml to restrict component exportation to only those components intended to be accessible externally.

Potential Impact

For European organizations, the impact of this vulnerability depends largely on the usage of the affected application 'Modo Legend of the Phoenix' within their environment. If the app is used internally or by employees on corporate devices, the improper export of components could lead to unauthorized access to sensitive data or internal app functions, potentially enabling lateral movement or data leakage within the device. Since the attack requires local access, the risk is higher in environments where device security is lax or where employees install untrusted applications. The public availability of exploit code increases the likelihood of opportunistic attacks, especially in environments with shared or less controlled devices. However, the medium severity and local attack vector limit the scope of impact primarily to compromised or physically accessed devices rather than remote exploitation. Organizations handling sensitive or regulated data should be cautious, as any unauthorized access or data manipulation could lead to compliance issues under GDPR or other data protection regulations. Additionally, the lack of vendor response and absence of patches mean organizations must rely on mitigation strategies until an official fix is available.

Mitigation Recommendations

1. Restrict installation of untrusted or unnecessary applications on devices running 'Modo Legend of the Phoenix' to reduce the risk of local exploitation. 2. Implement mobile device management (MDM) solutions to enforce application whitelisting and restrict sideloading of apps. 3. Educate users on the risks of installing unknown or unverified applications and the importance of device security hygiene. 4. Monitor devices for unusual behavior that could indicate exploitation attempts, such as unexpected inter-process communication or component invocation. 5. If possible, disable or limit the usage of the affected app until a vendor patch or update is released. 6. For organizations developing or deploying Android apps, review AndroidManifest.xml files to ensure components are not exported unless explicitly required, using android:exported="false" where appropriate. 7. Regularly audit device security policies and update them to address emerging threats like this one. 8. Consider network segmentation and endpoint protection to limit the impact of compromised devices.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-08-29T10:28:58.703Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68b218fcad5a09ad007b7a34

Added to database: 8/29/2025, 9:17:48 PM

Last enriched: 8/29/2025, 9:32:46 PM

Last updated: 8/29/2025, 9:59:08 PM

Views: 3

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

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

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats