RepairitApplication · Wondershare

CVE-2025-10644

CRITICAL · 9.4 CVSS v3.0 Published 2025-09-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Wondershare Repairit SAS Token Incorrect Permission Assignment Authentication Bypass Vulnerability. This vulnerability allows remote attackers to bypass authentication on Wondershare Repairit. Authentication is not required to exploit this vulnerability. The specific flaw exists within the permissions granted to an SAS token. An attacker can leverage this vulnerability to launch a supply-chain attack and execute arbitrary code on customers' endpoints. Was ZDI-CAN-26892.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This vulnerability in Wondershare Repairit involves incorrect permission assignment on an SAS (Shared Access Signature) token, which allows remote attackers to bypass authentication entirely. The flaw enables attackers to launch supply-chain attacks and achieve arbitrary code execution on customer endpoints without requiring any credentials.

MitigationOrganizations using Wondershare Repairit should immediately check for and apply any available security updates from the vendor. Until a patch is available, network segmentation and monitoring for suspicious activity related to the software should be implemented as compensating controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RepairitApplication
Affected:= 6.5.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify installed version of Wondershare Repairit
    Check the application version through the software's About section, Help menu, or by right-clicking the executable file and selecting Properties to view version information
    Affected if The installed version is exactly 6.5.2
  2. Identify SAS token configuration files
    Search the application installation directory and user configuration folders for files containing SAS token or Shared Access Signature references - look for patterns like *.config, *.json, or token-related files
    Affected if SAS token configuration files exist and are accessible within the application directories
  3. Review network communication behavior
    Monitor the application network traffic using a packet capture tool or network monitor to observe any outbound connections that may be using SAS token authentication
    Affected if The application makes network requests that bypass normal authentication prompts or use exposed SAS tokens
  4. Check for unauthorized access indicators
    Review application and system logs for any unexpected download activity, software updates, or file modifications that occurred without user initiation
    Affected if Log entries show software update or file download events that were not initiated by an authenticated user

A system is affected if Wondershare Repairit version 6.5.2 is installed and the application exposes SAS tokens that allow unauthenticated network access or file modifications.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Organizations using Wondershare Repairit should immediately check for and apply any available security updates from the vendor. Until a patch is available, network segmentation and monitoring for suspicious activity related to the software should be implemented as compensating controls.

Fix this in Repairit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,480
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10644 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10644 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data