dbcve.org
Total SecurityApplication · Quickheal

CVE-2025-69875

HIGH · 7.8 CVSS v3.1 Published 2026-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
A vulnerability exists in Quick Heal Total Security 23.0.0 in the quarantine management component where insufficient validation of restore paths and improper permission handling allow a low-privileged local user to restore quarantined files into protected system directories. This behavior can be abused by a local attacker to place files in high-privilege locations, potentially leading to privilege escalation.

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

Quick Heal Total Security 23.0.0 has a vulnerability in its quarantine management component where insufficient validation of restore paths combined with improper permission handling allows a low-privileged local user to restore quarantined files into protected system directories. This enables a local attacker to escalate privileges by placing files in high-privilege locations.

MitigationApply vendor patch when released. Until then, restrict local user access to quarantine management functionality and monitor for suspicious file restore operations to protected system directories.

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
Total SecurityApplication
Affected:= 23.0.0

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Confirm Quick Heal Total Security installation and version
    Check installed programs or use command 'reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall" /s | findstr -i "Quick Heal"' or look in Add/Remove Programs for Quick Heal Total Security version 23.0.0
    Affected if Quick Heal Total Security version 23.0.0 is installed
  2. Identify quarantine database or storage location
    Look for quarantine-related folders in Quick Heal installation directory (typically C:\Program Files\Quick Heal\Total Security\) or user-accessible quarantine folders
    Affected if Quarantine management component stores files in locations accessible to low-privileged users
  3. Verify restore functionality is accessible to standard users
    Attempt to use Quick Heal's quarantine restore feature as a non-admin user, or check file/folder permissions on quarantine and restore directories allowing write access for Users group
    Affected if Standard low-privileged users have permissions to initiate file restore operations
  4. Monitor for restore operations targeting protected directories
    Use process monitoring (e.g., Sysmon Event ID 11 or file audit logs) to watch for Quick Heal processes writing files to system directories (C:\Windows\System32\, C:\Program Files\)
    Affected if Restore operations can target protected system directories outside user-controlled paths
  5. Check for recent unauthorized file placements in system directories
    Review creation timestamps of executable files in C:\Windows\System32\ or C:\Program Files\ that correlate with Quick Heal quarantine restore activity
    Affected if Unexpected executable or DLL files appear in system directories following quarantine restore actions

A user is affected if Quick Heal Total Security 23.0.0 is installed and the quarantine restore feature permits low-privileged users to write files to protected system directories, enabling privilege escalation.

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

Apply vendor patch when released. Until then, restrict local user access to quarantine management functionality and monitor for suspicious file restore operations to protected system directories.

Fix this in Total Security Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-69875 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