CVE-2025-63435VulnerabilityPublished 24 Nov 2025

CVE-2025-63435: n/a

Source CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.3Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: 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 24 Nov 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 2026-10-26.

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

AI-suggested

Organizations should implement network-level controls to restrict access to the update server endpoint, such as IP whitelisting or VPN requirements, to limit unauthorized downloads. Monitoring and logging access to update package endpoints can help detect unusual or unauthorized download activity. Until an official patch or update is released by Xtooltech, organizations should consider isolating devices running Xtool AnyScan from untrusted networks or using application-layer firewalls to control outbound update requests. Additionally, validating the integrity and authenticity of update packages locally using cryptographic signatures can help ensure that downloaded updates are legitimate and unaltered. Engaging with the vendor to obtain timelines for patches or mitigations and applying updates promptly once available is critical. Security teams should also educate users about the risks and monitor for any suspicious activity related to the application.

Description

CVE-2025-63435 is a medium severity vulnerability in the Xtooltech Xtool AnyScan Android application version 4.40.40, where the server-side endpoint serving update packages lacks authentication. This allows unauthenticated remote attackers to freely download official update packages. Although the vulnerability does not allow modification or disruption of the update packages, unauthorized access to these packages could facilitate reconnaissance or indirect attacks. The vulnerability does not require user interaction and has a low complexity of exploitation. No known exploits are currently reported in the wild. European organizations using this application should be aware of potential information disclosure risks and monitor for suspicious activity related to update package downloads.

Impact

For European organizations, the primary impact of this vulnerability lies in potential information disclosure. Attackers could download update packages to analyze them for weaknesses or to understand the update process, which might aid in crafting more sophisticated attacks against the application or its users. While the vulnerability does not allow modification of update packages or direct compromise of systems, it could be leveraged as part of a broader attack chain. Organizations relying on Xtooltech Xtool AnyScan for security scanning or diagnostics may face risks if attackers use the disclosed information to evade detection or exploit other vulnerabilities. The lack of authentication on the update endpoint also raises concerns about supply chain security and trustworthiness of update delivery. Given the medium severity and absence of known exploits, the immediate risk is moderate but should not be ignored, especially in sectors where Xtool AnyScan is widely used for critical operations.

Summary

The vulnerability identified as CVE-2025-63435 affects the Xtooltech Xtool AnyScan Android application version 4.40.40. The core issue is a missing authentication mechanism on the server-side endpoint responsible for distributing update packages to the application. This endpoint allows any unauthenticated remote attacker to download official update packages without restriction. While the vulnerability does not permit modification or injection of malicious code into the update packages, the ability to freely download these packages can enable attackers to analyze the update contents for vulnerabilities or gain insights into the application's update mechanisms. The vulnerability is classified under CWE-306 (Missing Authentication for Critical Function), indicating a failure to enforce proper access controls on sensitive operations. The CVSS v3.1 base score is 4.3 (medium), reflecting the network attack vector, low attack complexity, no user interaction, and limited confidentiality impact, with no impact on integrity or availability. No patches or mitigations have been published yet, and no exploits are known to be active in the wild. The vulnerability's impact is primarily on confidentiality, as unauthorized access to update packages could reveal sensitive information or facilitate further targeted attacks.

CWE-306Missing Authentication for Critical Function (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #21OWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
Architecture and Design
Divide the software into anonymous, normal, privileged, and administrative areas. Identify which of these areas require a proven user identity, and use a centralized authentication capability.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Architecture and Design
Where possible, avoid implementing custom, "grow-your-own" authentication routines and consider using authentication capabilities as provided by the surrounding framework, operating system, or environment.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V1.2.3 (opens in a new tab)
V1.2.2 (opens in a new tab)
V1.2.4 (opens in a new tab)
Attack patterns
Choosing Message Identifier (opens in a new tab)
Force the System to Reset Values (opens in a new tab)
Using Unpublished Interfaces or Functionality (opens in a new tab)
Cross Site Request Forgery (opens in a new tab)
Communication Channel Manipulation (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

Description

AI analysisMachine-generated, updated 1 Dec 2025, 17:45 UTC

WeaknessesCWE-306

Technical details

References

Community reviews

Related threats