CVE-2025-10643VulnerabilityPublished 17 Sep 2025

CVE-2025-10643: Wondershare Repairit · Incorrect Permissions

Affects Wondershare RepairitSource CVE Database V5

Not known to be exploited · CVSS 9.1 Critical.

Data as of 26 Oct 2026, 08:11 UTC

CVSS 3.0 base score

9.1Critical

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 17 Sep 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

Affected software

Product	Affected	Fixed in
Wondershare Repairit	Affected =6.5.2	Fixed in–

AI-suggested

1. Immediate upgrade or patching: Organizations should monitor Wondershare's official channels for patches addressing CVE-2025-10643 and apply them as soon as they become available. 2. Temporary access controls: Until a patch is available, restrict network access to systems running Wondershare Repairit 6.5.2, especially from untrusted or external networks, using firewalls or network segmentation. 3. Monitor and audit: Implement enhanced logging and monitoring around the use of Wondershare Repairit, focusing on unusual access patterns or unauthorized attempts to use the storage account token. 4. Least privilege principle: Review and minimize permissions related to storage account tokens and related resources to limit potential exploitation scope. 5. Incident response readiness: Prepare incident response plans specifically for exploitation scenarios involving authentication bypass to ensure rapid containment and remediation. 6. Vendor engagement: Engage with Wondershare support for guidance and to obtain any interim mitigation advice or beta patches. 7. User awareness: Inform relevant IT and security personnel about the vulnerability to ensure vigilance and prompt reporting of suspicious activity.

Description

Wondershare Repairit Incorrect Permission Assignment Authentication Bypass Vulnerability. This vulnerability allows remote attackers to bypass authentication on affected installations of Wondershare Repairit. Authentication is not required to exploit this vulnerability. The specific flaw exists within the permissions granted to a storage account token. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-26902.

Impact

For European organizations using Wondershare Repairit 6.5.2, this vulnerability poses a significant risk. Since the flaw allows authentication bypass remotely without any user interaction, attackers can potentially access sensitive data or system functions that should be protected. This could lead to unauthorized data disclosure, data tampering, or further lateral movement within the network. Organizations in sectors such as finance, healthcare, legal, and critical infrastructure, where data integrity and confidentiality are paramount, are particularly at risk. The breach of sensitive repair or recovery data could also impact operational continuity and compliance with stringent European data protection regulations like GDPR. Additionally, the reputational damage and potential regulatory penalties resulting from exploitation could be severe. Given the critical severity and ease of exploitation, the threat could be leveraged for espionage, sabotage, or ransomware deployment if combined with other vulnerabilities or attack vectors.

CWE-732Incorrect Permission Assignment for Critical Resource (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
Implementation
When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user), and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
Architecture and Design
Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly.
Architecture and Design · Operation · Sandbox or Jail
Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.3.3 (opens in a new tab)
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Directory Indexing (opens in a new tab)
Using Malicious Files (opens in a new tab)
Exploiting Incorrectly Configured Access Control Security Levels (opens in a new tab)
Signing Malicious Code (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

zerodayinitiative.com/advisories/ZDI-25-895/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Sep 2025, 00:40 UTC

WeaknessesCWE-732

Technical details

References

Community reviews

Related threats