XiaomiApplication · Mi

CVE-2020-14130

MEDIUM · 5.3 CVSS v3.1 Published 2021-09-16
Fix available
A fix is available. Upgrade to 3.0.210809 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable 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
Some js interfaces in the Xiaomi community were exposed, causing sensitive functions to be maliciously called on Xiaomi community app Affected Version <3.0.210809

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 · moderate confidence

The Xiaomi community app versions prior to 3.0.210809 exposed JavaScript interfaces that allowed malicious calls to sensitive native functions. This typically occurs when WebView components improperly expose @JavascriptInterface-annotated methods to untrusted web content, enabling attackers to invoke privileged mobile functions through crafted JavaScript.

MitigationUpgrade Xiaomi community app to version 3.0.210809 or later. If upgrade is not immediately possible, consider disabling JavaScript interface exposure to untrusted WebView content or implementing additional input validation on exposed methods.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
XiaomiApplication
Affected:< 3.0.210809

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

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 Xiaomi community app version
    Open device Settings > Apps > Xiaomi Community (or Xiaomi Forum) and view the version information displayed under the app name, or query via adb: adb shell dumpsys package com.xiaomi.market | grep versionName
    Affected if Version shown is less than 3.0.210809 (for example, 3.0.210701, 2.9.x, or any version without the 3.0.210809 build)
  2. Confirm WebView usage in the app
    Inspect app network traffic or review app manifest (via adb: adb shell dumpsys package com.xiaomi.market | grep -i webview) to determine if WebView components load remote web content
    Affected if WebView loads untrusted URLs and JavaScript execution is enabled
  3. Verify JavaScript interface exposure
    Analyze the app APK or decompiled code for @JavascriptInterface annotations on native methods that are reachable from WebView (methods decorated with @JavascriptInterface and accessible via the jsbridge or similar interface names like 'android' or custom bridge names)
    Affected if Any @JavascriptInterface-annotated methods are exposed to WebView content without additional origin validation

The environment is affected if the Xiaomi community app is installed with a version lower than 3.0.210809 and the app uses WebView to load untrusted content with exposed JavaScript interfaces.

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
Upgrade available Upgrade to 3.0.210809 or later
Fixed in 3.0.210809
Interim mitigation

Upgrade Xiaomi community app to version 3.0.210809 or later. If upgrade is not immediately possible, consider disabling JavaScript interface exposure to untrusted WebView content or implementing additional input validation on exposed methods.

Recommended fix Moderate confidence

3.0.210809 or later

  1. Open the Xiaomi community app on your device
  2. Navigate to the app settings or profile section
  3. Check the current app version under 'About' or 'Version'
  4. If the version is earlier than 3.0.210809, update the app through the Xiaomi app store, Google Play Store, or by downloading the latest version from Xiaomi's official website
  5. After updating, verify the version number shows 3.0.210809 or later

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

Fix this in Xiaomi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2020-14130 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