CVE-2025-69875
Improper Permission Handling in Quick Heal Quarantine Enables Privilege Escalation
Publication date: 2026-02-03
Last updated on: 2026-02-11
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| quickheal | total_security | 23.0.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-552 | The product makes files or directories accessible to unauthorized actors, even though they should not be. |
| CWE-269 | The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. |
| CWE-281 | The product does not preserve permissions or incorrectly preserves permissions when copying, restoring, or sharing objects, which can cause them to have less restrictive permissions than intended. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-69875 is a local privilege escalation vulnerability in Quick Heal Total Security version 23.0.0, specifically in its quarantine management component.
The vulnerability occurs because the software does not properly validate restore paths and mishandles permissions when restoring quarantined files.
A low-privileged local user can exploit this flaw by mounting a quarantined file and triggering the restore operation, which is executed by a high-privileged Quick Heal service.
Due to insufficient path validation and lack of permission checks, the attacker can force the service to write files into protected system directories like System32.
This allows placing files with elevated privileges, potentially leading to privilege escalation.
How can this vulnerability impact me? :
This vulnerability allows a low-privileged local attacker to write arbitrary files into high-integrity system directories.
The impact includes local privilege escalation, where the attacker can gain higher system privileges than originally granted.
Additionally, the attacker could perform service or DLL hijacking, enabling execution of attacker-controlled binaries with elevated privileges.
No special system conditions or prior elevated privileges are required to exploit this vulnerability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves monitoring for unauthorized writes by Quick Heal services to protected system directories such as System32.
Since the vulnerability allows a low-privileged user to restore quarantined files into high-privilege locations, you can check for unexpected or suspicious files in these directories that may have been recently created or modified by Quick Heal services.
Commands to assist detection could include:
- On Windows, use PowerShell to list recently modified files in protected directories, for example: Get-ChildItem -Path C:\Windows\System32 -Recurse | Where-Object { $_.LastWriteTime -gt (Get-Date).AddDays(-1) }
- Check running Quick Heal services and their permissions using: sc queryex QuickHealServiceName (replace with actual service name)
- Audit file system access events for Quick Heal processes using Windows Event Viewer or audit policies to detect unauthorized file writes.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in Quick Heal Total Security 23.0.0 allows a low-privileged local user to restore quarantined files into protected system directories, potentially leading to privilege escalation and unauthorized file writes in high-integrity locations.
Such unauthorized privilege escalation and improper permission handling could lead to violations of security controls required by common standards and regulations like GDPR and HIPAA, which mandate strict access controls and protection of sensitive data.
However, the provided information does not explicitly discuss the direct impact on compliance with these standards or any regulatory implications.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps before a patch is available include:
- Disable or restrict quarantine mount and restore capabilities for non-administrator users to prevent exploitation by low-privileged accounts.
- Monitor protected system directories for unauthorized writes by Quick Heal services to detect and respond to potential exploitation attempts.
- Apply policy rules or access control restrictions to prevent unauthorized restoration of quarantined files to system paths.