dbcve.org
SuperantispywareApplication

CVE-2025-14491

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-27660.

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 local attackers to escalate privileges from low-privileged code execution to full SYSTEM-level code execution. This is a classic local privilege escalation (LPE) flaw where the service exposes a callable function without proper access control validation.

MitigationApply the vendor patch for CVE-2025-14491 when available, or contact RealDefense for remediation. If no patch is imminent, consider removing SUPERAntiSpyware from systems where it's not critically required, as the software runs with elevated privileges.

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 if SUPERAntiSpyware is installed
    Look for SUPERAntiSpyware in Program Files or Program Files (x86) directories, or check the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'SUPERAntiSpyware'
    Affected if The software is installed on the system
  2. Identify the installed version
    Locate the version information in the registry at HKLM\SOFTWARE\SUPERAntiSpyware or in the program's main executable file properties, or run: wmic product where "name like 'SUPERAntiSpyware'" get version
    Affected if The installed version is lower than 10.0.1280 (e.g., 10.0.x.x where x < 1280, or any version 9.x)
  3. Verify the SAS Core Service exists and is running
    Open Services.msc and look for 'SAS Core Service' or run: sc query SASCoreService in Command Prompt
    Affected if The SAS Core Service is present and running on the system
  4. Confirm the service runs with elevated privileges
    Run: sc qc SASCoreService to check the service configuration, then check the service's binary path and verify it executes with SYSTEM-level privileges
    Affected if The service is configured to run as LocalSystem or with elevated privileges
  5. Check for exposed callable interface
    Examine the service's registered RPC or named pipe endpoints by reviewing the service's configuration or using tools like 'tasklist /svc' to confirm SASCoreService.exe is actively running as a privileged process
    Affected if The SAS Core Service is running as a privileged process accessible to low-privileged users

A user is affected if SUPERAntiSpyware version is below 10.0.1280 AND the SAS Core Service is installed and running with SYSTEM-level privileges, allowing a low-privileged attacker to invoke the dangerous exposed function for 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.

dbcve · scoped
Upgrade available Upgrade to 10.0.1280 or later
Fixed in 10.0.1280
Interim mitigation

Apply the vendor patch for CVE-2025-14491 when available, or contact RealDefense for remediation. If no patch is imminent, consider removing SUPERAntiSpyware from systems where it's not critically required, as the software runs with elevated privileges.

Recommended fix High confidence

SUPERAntiSpyware 10.0.1280 or later

  1. 1. Download the latest version of SUPERAntiSpyware from the official vendor website
  2. 2. Ensure you have administrative privileges on the target system
  3. 3. Close any running instances of SUPERAntiSpyware
  4. 4. Run the installer for version 10.0.1280 or later
  5. 5. Follow the installation wizard prompts to complete the upgrade
  6. 6. Verify the installed version is 10.0.1280 or higher via Help > About in the application

Generated from the published advisory — verify against the referenced sources before acting.

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-14491 — 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-14491 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