CVE-2025-57625
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 · uneditedCYRISMA Sensor before 444 for Windows has an Insecure Folder and File Permissions vulnerability. A low-privileged user can abuse these issues to escalate privileges and execute arbitrary code in the context of NT AUTHORITY\SYSTEM by replacing DataSpotliteAgent.exe or any other binaries called by the Cyrisma_Agent service when it starts
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 · high confidenceCYRISMA Sensor before version 444 for Windows contains insecure folder and file permissions in its installation directory. A low-privileged user can replace the DataSpotliteAgent.exe binary or other service-called executables with a malicious payload. When the Cyrisma_Agent service restarts, it executes the attacker-controlled binary with NT AUTHORITY\SYSTEM privileges, achieving local privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Locate CYRISMA Sensor installationSearch for the CYRISMA Sensor installation directory, typically under Program Files or Program Files (x86). Look for a folder named 'CYRISMA' or containing DataSpotliteAgent.exe.Affected if CYRISMA Sensor is found installed on the system
-
Identify installed versionRight-click on DataSpotliteAgent.exe in the installation folder, select Properties, and check the File Version or Product Version on the Details tab. Alternatively, run: (Get-Item 'C:\Path\To\DataSpotliteAgent.exe').VersionInfoAffected if The version number is lower than 444 (e.g., 443, 400, etc.)
-
Verify folder permissionsRight-click the CYRISMA installation folder, go to Properties > Security tab, and review the permissions for Users or non-admin groups. Check if Write or Modify permissions are granted to standard users.Affected if Non-admin users have Write or Full Control permissions to the installation folder
-
Check executable file permissionsRight-click on DataSpotliteAgent.exe, select Properties > Security, and verify if Users or non-admin accounts have Write permissions on the executable file itself.Affected if Standard users can modify or replace DataSpotliteAgent.exe
-
Confirm Cyrisma_Agent service existsOpen Services (services.msc) and look for a service named 'Cyrisma_Agent', or run: Get-Service -Name '*Cyrisma*'Affected if The Cyrisma_Agent service is present and configured to run
A system is affected if CYRISMA Sensor is installed with a version below 444 AND non-admin users have write access to the installation folder or DataSpotliteAgent.exe, allowing potential privilege escalation when the service restarts.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade CYRISMA Sensor to version 444 or later. If immediate patching is not possible, audit and restrict NTFS permissions on the CYRISMA installation folder to prevent write access for non-admin users.
CYRISMA Sensor version 444 for Windows
- Obtain the CYRISMA Sensor version 444 installer from the official vendor or authorized download channel
- Stop the Cyrisma_Agent Windows service if it is currently running
- Uninstall the current (vulnerable) version of CYRISMA Sensor from the Windows system
- Install CYRISMA Sensor version 444 using the official installer
- Verify the installation completed successfully and the service is running
- Confirm that the file permissions on the CYRISMA Sensor installation directory and binaries (including DataSpotliteAgent.exe) are now correctly restricted
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-57625 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-57625 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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