dbcve.org
SuperantispywareApplication

CVE-2025-14494

HIGH · 7.8 CVSS v3.0 Published 2025-12-23
Fix available
A fix is available. Upgrade to 10.0.1280 or later.
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
RealDefense SUPERAntiSpyware Exposed Dangerous Function Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of RealDefense SUPERAntiSpyware. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the SAS Core Service. The issue results from an exposed dangerous function. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of SYSTEM. Was ZDI-CAN-27676.

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 · moderate confidence

The vulnerability exists in the SAS Core Service of SUPERAntiSpyware, where an exposed dangerous function allows a local attacker with low-privileged code execution to escalate privileges to SYSTEM context and execute arbitrary code. This is a classic local privilege escalation (LPE) flaw where the service improperly exposes functionality that should be restricted.

MitigationApply the vendor-supplied patch for CVE-2025-14494 when available. Until then, restrict user access to the SAS Core Service binaries and configuration files, and monitor for unauthorized service manipulation attempts.

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
SuperantispywareApplication
Affected:< 10.0.1280

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.0/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. Check installed SUPERAntiSpyware version
    Open Programs and Features (appwiz.cpl) or check the program's About/Help section to find the installed version number
    Affected if The version listed is lower than 10.0.1280 (e.g., 10.0.xxxx where xxxx is less than 1280)
  2. Identify SAS Core Service
    Open Services (services.msc) and look for a service named 'SAS Core Service' or similar, or run 'sc queryex type= service state= all' to enumerate all services
    Affected if A SAS Core Service entry exists and is running on the system
  3. Check SAS Core Service binary location
    Use 'sc qc "SAS Core Service"' (or the discovered service name) to query the service configuration and identify the binary path, then verify the file exists
    Affected if The service binary path is found and points to a file within the SUPERAntiSpyware installation directory
  4. Inspect service binary file permissions
    Right-click the service binary file, go to Properties > Security, or run 'icacls "<path_to_binary>"' to view ACLs
    Affected if Users with low-privileged accounts (Non-Admin users) have Write or Write+Execute permissions on the service binary or its folder
  5. Check for service modification access
    Run 'sc sdset "SAS Core Service"' to view the security descriptor, or verify if standard users can stop/start the service via 'sc stop/stop' or Task Manager
    Affected if Non-admin users have permission to stop, start, or modify the service configuration

Your system is affected if SUPERAntiSpyware version is below 10.0.1280 AND the SAS Core Service is installed and accessible to low-privileged users, allowing potential privilege escalation to SYSTEM context.

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
Upgrade available Upgrade to 10.0.1280 or later
Fixed in 10.0.1280
Interim mitigation

Apply the vendor-supplied patch for CVE-2025-14494 when available. Until then, restrict user access to the SAS Core Service binaries and configuration files, and monitor for unauthorized service manipulation attempts.

Fix this in Superantispyware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14494 — 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-14494 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