dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-50862

MEDIUM · 5.9 CVSS v3.1 Published 2025-08-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
64/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Lotus Cars Android app version 1.2.8 has android:allowBackup="true" set in its AndroidManifest.xml, which permits full application data backup via Android Debug Bridge (ADB) backup commands. On rooted devices or devices with USB debugging enabled, attackers can extract sensitive user data from the app's private storage directories.

MitigationSet android:allowBackup="false" in the AndroidManifest.xml file, rebuild the application, and release an updated version to users.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Lotus Cars app version
    Run 'adb shell pm list packages | grep lotus' to find the package name, then 'adb shell pm dump <package_name> | grep versionName' to get the version
    Affected if Version is 1.2.8
  2. Check allowBackup setting in AndroidManifest.xml
    Decompile the APK (using apktool) and inspect AndroidManifest.xml for android:allowBackup="true" attribute
    Affected if android:allowBackup is set to true (or the attribute is missing, which defaults to true in older Android versions)
  3. Verify USB debugging status on device
    On the device, go to Settings > Developer Options > USB debugging, or run 'adb get-state' to check if ADB debugging is enabled
    Affected if USB debugging is enabled on the device
  4. Check for root access or rooting status
    Run 'adb shell su -c id' or use a root checker app to determine if the device has root privileges
    Affected if Device has root access or is a rooted device

The environment is affected if the Lotus Cars Android app version 1.2.8 is installed with allowBackup="true" in the manifest AND the device has USB debugging enabled or root access, allowing unauthorized backup extraction of app data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Set android:allowBackup="false" in the AndroidManifest.xml file, rebuild the application, and release an updated version to users.

Recommended fix Moderate confidence
  1. Open the AndroidManifest.xml file in the project source code
  2. Locate the <application> tag element
  3. Add or modify the android:allowBackup attribute to set it to false: android:allowBackup="false"
  4. Rebuild and redistribute the app with this configuration change

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-50862 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-50862 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data