VulnerabilityPublished 16 Apr 2025Updated 9 Sep 2025

CVE-2025-3698: TECNO com.transsion.carlcare · Exposed Dangerous Method or Function

Affects TECNO com.transsion.carlcareSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 3.1 base score

7.5High

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

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

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

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

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Apr 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 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

Affected software

Product	Affected	Fixed in
TECNO com.transsion.carlcare	Affected =6.2.7	Fixed in–

AI-suggested

Given the absence of an official patch at the time of publication, European organizations should take proactive and specific measures beyond generic advice: 1. Inventory and Audit: Identify all devices within the organization that have the 'com.transsion.carlcare' app installed, particularly version 6.2.7. 2. Application Control: Implement mobile device management (MDM) policies to restrict or remove the vulnerable app from corporate-managed devices. 3. Network Segmentation: Limit network access from devices running the vulnerable app to sensitive corporate resources to reduce the risk of data leakage. 4. Monitor Network Traffic: Deploy network monitoring tools to detect unusual outbound traffic patterns that may indicate exploitation attempts targeting the app. 5. User Awareness: Educate users about the risks of using vulnerable applications and encourage updating or uninstalling the app if possible. 6. Vendor Engagement: Engage with TECNO or Transsion Holdings to obtain timelines for patches or mitigations and request security updates. 7. Application Hardening: For organizations developing or managing similar apps, review interface exposure and restrict access to dangerous methods or functions. 8. Incident Response Preparedness: Prepare to respond to potential data leakage incidents by having detection and containment procedures in place.

Description

Interface exposure vulnerability in the mobile application (com.transsion.carlcare) may lead to information leakage risk.

Impact

For European organizations, the primary impact of this vulnerability lies in the potential leakage of sensitive information through the TECNO Carlcare mobile application. While TECNO devices and apps are more prevalent in African and some Asian markets, their presence in Europe is limited but growing, especially in immigrant communities and niche markets. Organizations that rely on or support employees using TECNO devices may face risks of data leakage if the vulnerable app is installed on corporate or personal devices used for work purposes. The information leakage could expose confidential corporate data, user credentials, or personally identifiable information (PII), leading to privacy violations, regulatory non-compliance (e.g., GDPR), and reputational damage. Since the vulnerability does not affect integrity or availability, it is less likely to cause service disruption but can facilitate further attacks if sensitive data is obtained. The lack of required privileges or user interaction increases the risk of automated exploitation attempts, potentially targeting European users of the app. Additionally, organizations in sectors with high privacy requirements, such as finance, healthcare, and government, may be more sensitive to such leaks.

CWE-749Exposed Dangerous Method or Function (opens in a new tab)
Base weaknessLikelihood of exploit: LowOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product provides an Applications Programming Interface (API) or similar interface for interaction with external actors, but the interface includes a dangerous method or function that is not properly restricted.
Architecture and Design
If you must expose a method, make sure to perform input validation on all arguments, limit access to authorized parties, and protect against all possible vulnerabilities.
Architecture and Design · Implementation · Attack Surface Reduction
Identify all exposed functionality. Explicitly list all functionality that must be exposed to some user or set of users. Identify which functionality may be: accessible to all users; restricted to a small set of privileged users; prevented from being directly accessible at all
OWASP Cheat Sheets
Third Party Javascript Management (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V14.5.1 (opens in a new tab)
V10.1.1 (opens in a new tab)
V1.4.4 (opens in a new tab)
Attack patterns
WebView Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Sep 2025, 23:50 UTC

WeaknessesCWE-749

Technical details

References

Community reviews

Related threats