CVE-2025-50862: The Lotus Cars Android app (com.lotus.carsdomestic.intl) 1.2.8 has allowBackup=true set in its manifest, al...
The Lotus Cars Android app (com.lotus.carsdomestic.intl) 1.2.8 has allowBackup=true set in its manifest, allowing data exfiltration via ADB backup on rooted or debug-enabled devices. This presents a risk of user data exposure.
Security readout for executives and security teams
Plain-English summary
CVE-2025-50862 is a data exposure weakness in the Lotus Cars Android app version 1.2.8. The app reportedly allows Android backup, which may expose app data on rooted or debug-enabled devices. The business risk is user data leakage, mainly where device controls are weak.
Executive priority
Treat as a moderate mobile data-exposure issue. It is not described as remotely exploitable or actively exploited, but fleets with rooted or debug-enabled devices should act promptly.
Technical view
The source states com.lotus.carsdomestic.intl 1.2.8 has android:allowBackup=true in its manifest. This can permit app data extraction through Android backup on rooted or debug-enabled devices. CVSS 3.1 is 5.9 with local attack vector and low complexity.
Likely exposure
Exposure appears limited to users or managed devices running the identified Lotus Cars Android app version 1.2.8, especially rooted, debug-enabled, developer, or poorly controlled Android devices.
Exploitation context
The bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation is local and depends on device state, but could still matter if sensitive app data is stored unprotected.
Researcher notes
Evidence is thin: the CVE description names the package and version, while structured affected fields are n/a. No vendor advisory, patch version, exploit-in-the-wild report, or detailed impact data is included.
Mitigation direction
Check Lotus or app-store guidance for an updated release or vendor fix.
Prioritize updating or removing version 1.2.8 where deployed.
Block rooted or debug-enabled Android devices from corporate access.
Use MDM controls to restrict Android debugging on managed devices.
Avoid storing sensitive account data in the app until guidance is available.
Validation and detection
Inventory Android devices for package com.lotus.carsdomestic.intl version 1.2.8.
Confirm whether deployed APK manifests set allowBackup=true.
Identify rooted, debug-enabled, or unmanaged Android devices using the app.
Monitor the CVE record and researcher reference for vendor updates.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-200 · source CWE mapping
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.