dbcve.org
SuperantispywareApplication

CVE-2025-14492

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

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

A local privilege escalation vulnerability exists in the SUPERAntiSpyware SAS Core Service. The flaw stems from an exposed dangerous function within the service that allows a low-privileged attacker to execute arbitrary code in the SYSTEM context. An attacker requires the ability to execute low-privileged code on the target system as a prerequisite to exploit this vulnerability.

MitigationApply the vendor-supplied patch for SUPERAntiSpyware when released. In the interim, restrict local user access to the SAS Core Service and monitor for any 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. Verify SUPERAntiSpyware installation
    Look for the program directory at C:\Program Files\SUPERAntiSpyware\ or check Add/Remove Programs for SUPERAntiSpyware entry
    Affected if SUPERAntiSpyware is installed on the system
  2. Identify installed version
    Check the version by viewing the version info of the main executable (usually SUPERAntiSpyware.exe in the install directory) or by querying the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\SUPERAntiSpyware
    Affected if The installed version is lower than 10.0.1280
  3. Confirm SAS Core Service presence
    Open Services console (services.msc) or run 'sc query' command and look for a service named 'SAS Core Service' or similar
    Affected if The SAS Core Service is present and running on the system
  4. Check service executable path
    Run 'sc qc "SAS Core Service"' (or the actual service name found) to retrieve the executable path configured for the service
    Affected if The service points to a SUPERAntiSpyware executable in a user-writable location

A user is affected if SUPERAntiSpyware version is below 10.0.1280 and the SAS Core Service is installed and running on the 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-supplied patch for SUPERAntiSpyware when released. In the interim, restrict local user access to the SAS Core Service and monitor for any unauthorized service manipulation attempts.

Recommended fix Moderate confidence

SuperAntiSpyware version 10.0.1280 or later

  1. 1. Verify the current SuperAntiSpyware version by opening the application and checking About/Help menu, or right-clicking the application in Programs and selecting Properties
  2. 2. If the installed version is below 10.0.1280, navigate to the official SuperAntiSpyware website to download the latest version
  3. 3. Download the most recent stable release (version 10.0.1280 or later) from the official vendor site
  4. 4. Close SuperAntiSpyware if it is currently running
  5. 5. Run the installer with administrative privileges
  6. 6. Follow the installation wizard prompts to complete the upgrade
  7. 7. After installation, verify the new version by checking About to confirm 10.0.1280 or later is installed
  8. 8. Restart the computer to ensure the SAS Core Service loads the updated version

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