dbcve.org
SuperantispywareApplication

CVE-2025-14496

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

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

This is a local privilege escalation vulnerability in the SAS Core Service component of RealDefense SUPERAntiSpyware. The flaw stems from an exposed dangerous function that allows a low-privileged attacker to elevate to SYSTEM context and execute arbitrary code. An attacker requires prior low-privileged code execution on the target system to exploit this vulnerability.

MitigationApply the vendor patch when released. Until then, restrict user access to the SAS Core Service and monitor for suspicious service interactions; consider compensating controls such as restricting who can interact with the service.

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. Verify SUPERAntiSpyware is installed
    Check for the product in Add/Remove Programs (appwiz.cpl) or look for installation directory at C:\Program Files\SUPERAntiSpyware or C:\Program Files (x86)\SUPERAntiSpyware
    Affected if Product is installed and version is below 10.0.1280
  2. Determine installed version number
    Right-click the SUPERAntiSpyware executable (usually in the installation folder), select Properties, and check the Details tab for Product Version. Alternatively, check the version in the program's About/Help section
    Affected if Version shown is less than 10.0.1280 (for example, 10.0.xxxx or earlier)
  3. Locate SAS Core Service
    Open Services (services.msc) and look for a service named 'SAS Core Service' or 'SUPERAntiSpyware Service' or similar. Or run 'sc query' from command prompt to list all services and search for 'SAS' or 'SuperAntiSpyware'
    Affected if The SAS Core Service exists on the system
  4. Check SAS Core Service status
    In Services console, right-click the SAS Core Service and select Properties, or run 'sc query [service_name]' to see if it is Running or Stopped
    Affected if Service is installed and Running (vulnerability requires the service to be active)
  5. Review service permissions
    Run 'sc sdshow [service_name]' from an elevated command prompt to view the Discretionary Access Control List (DACL). Check if non-admin users have permission to interact with the service (specifically SERVICE_INTERACTIVE_PROCESS or generic execute permissions)
    Affected if Low-privileged users have permissions to start/stop or interact with the service

You are affected if SUPERAntiSpyware version is below 10.0.1280 AND the SAS Core Service is installed and running on your system.

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 when released. Until then, restrict user access to the SAS Core Service and monitor for suspicious service interactions; consider compensating controls such as restricting who can interact with the service.

Recommended fix Moderate confidence

10.0.1280 or later

  1. 1. Visit the official SuperAntiSpyware website or use the built-in update mechanism within the application
  2. 2. Check the current installed version of SuperAntiSpyware (typically found in Help > About)
  3. 3. Download or update to version 10.0.1280 or later
  4. 4. Restart the system if required by the update process
  5. 5. Verify the update was successful by checking the version number again

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

Fix this in Superantispyware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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