VulnerabilityPublished 21 Jul 2025Updated 22 Jul 2025

CVE-2025-43976: The com.enflick.android.tn2ndLine application through 24.17.1.0 for Android enables any installed

Source CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Physical
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2025-43976, European organizations should: 1) Audit and restrict the installation of third-party apps, especially those from untrusted sources, to prevent malicious apps from being installed that could exploit this vulnerability. 2) Implement Mobile Device Management (MDM) solutions to control app permissions and monitor unusual calling behavior on corporate devices. 3) Educate users about the risks of installing apps from unknown developers and the importance of scrutinizing app permissions and behaviors. 4) Encourage or enforce the use of official, vetted communication apps rather than third-party dialers with known vulnerabilities. 5) Monitor telephony usage patterns for anomalies that could indicate unauthorized call activity. 6) Coordinate with the vendor (TextNow) to obtain patches or updates addressing this vulnerability and deploy them promptly once available. 7) Where possible, apply Android OS-level restrictions or security policies that limit inter-app communication or intent handling related to telephony functions. 8) Consider network-level controls to detect and block suspicious call patterns originating from devices known to have the vulnerable app installed.

Description

The com.enflick.android.tn2ndLine application through 24.17.1.0 for Android enables any installed application (with no permissions) to place phone calls without user interaction by sending a crafted intent via the com.enflick.android.TextNow.activities.DialerActivity component.

Impact

For European organizations, the impact of CVE-2025-43976 depends largely on the prevalence of the TextNow app within their user base or employee devices. Organizations with Bring Your Own Device (BYOD) policies or those in sectors where employees use third-party communication apps may face risks of unauthorized call initiation, leading to potential financial losses from toll fraud or reputational damage if fraudulent calls are traced back to corporate devices. Privacy concerns arise as unauthorized calls could expose sensitive information or allow attackers to leverage the device for further attacks. Additionally, the vulnerability could be exploited to disrupt communication channels, impacting operational continuity. While the vulnerability requires a malicious app to be installed, the lack of permission requirements lowers the barrier for exploitation. European telecom providers could also see indirect impacts if large numbers of devices are exploited, potentially affecting network resources. However, since the attack vector is local and no remote exploitation is possible, the threat is more contained to device-level compromise rather than large-scale network attacks.

References

Community reviews

Loading reviews…