CVE-2025-7892
BaseFortify
Publication date: 2025-07-20
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| idnow | idnow | to 9.6.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-926 | The Android application exports a component for use by other applications, but does not properly restrict which applications can launch the component or access the data it contains. |
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-7892 is a Task Hijacking vulnerability in the IDnow Android app (version 9.6.0 and earlier) caused by improper export of application components in the AndroidManifest.xml file. This allows malicious local applications to inherit permissions from the vulnerable app by exploiting these improperly exported components, potentially enabling attackers to manipulate tasks within the Android OS and phish user credentials. [1, 2]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access and manipulation of the IDnow app's components by malicious local applications. Attackers may hijack tasks to phish login credentials, compromising confidentiality, integrity, and availability of the app. Since the exploit requires local access and affects all Android versions prior to Android 11, it poses a moderate risk of credential theft and other security breaches. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by inspecting the AndroidManifest.xml file of the IDnow App (version 9.6.0 and earlier) to check for improperly exported application components in the de.idnow component. Since the vulnerability involves exported components, you can use Android debugging tools such as 'adb' to extract and analyze the manifest. For example, use the command 'adb shell pm dump de.idnow | grep -i exported' to identify exported components. Additionally, Google hacking techniques can be used to search for exposed AndroidManifest.xml files online to identify vulnerable targets. Local access to the device is required to perform these checks. [2, 1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves modifying the AndroidManifest.xml configuration to prevent improper export of application components, thereby blocking unauthorized task inheritance. Since no official fix or patch has been provided by the vendor, it is recommended to consider replacing the affected IDnow App with an alternative product. Limiting local access to the device and avoiding installation of untrusted applications can also reduce risk. [1, 2]