CVE-2025-10231
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 · uneditedAn Incorrect File Handling Permission bug exists on the N-central Windows Agent and Probe that, in the right circumstances, can allow a local low-level user to run commands with elevated permissions.
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 confidenceThis is a local privilege escalation vulnerability in N-central Windows Agent and Probe stemming from incorrect file handling permissions. A low-privileged local user can exploit improper permission assignments on certain files to execute arbitrary commands with elevated system or administrative 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< 2025.3CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if N-central Agent or Probe is installedCheck the system for N-able N-central Windows Agent or Probe components. Look for related services, processes, or installation directories. Common locations include Program Files and ProgramData directories.Affected if N-central Agent or Probe software is found on the system
-
Determine the installed N-central versionLocate version information for the installed Agent or Probe. Check registry keys, installed programs list, or version files within the installation directory.Affected if The installed version is any version prior to 2025.3 (the version number is less than 2025.3 or the exact version cannot be determined)
-
Identify the Agent and Probe installation directoriesFind the installation directories for the N-central Agent and Probe. These are typically under Program Files, Program Files (x86), or ProgramData with N-able or N-central in the path.Affected if Installation directories exist and contain Agent or Probe files
-
Examine file permissions on Agent/Probe directoriesReview the access control lists (ACLs) on the identified installation directories and their contents. Use icacls or similar tools to list permissions for non-administrative users.Affected if Non-administrative or low-privileged local users have write, modify, or full control permissions on executable files, configuration files, or DLLs within the Agent/Probe directories
-
Verify if low-privileged users can modify executable filesTest or review whether standard users can overwrite, delete, or modify .exe, .dll, .bat, .ps1, or other executable/script files in the installation directories.Affected if Standard users without administrative privileges can modify, replace, or delete executable or script files used by the Agent or Probe services
A user is affected if N-central Windows Agent or Probe is installed with a version prior to 2025.3 and low-privileged local users have write or modify permissions on files in the Agent/Probe installation directories that could be leveraged for privilege escalation.
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 · scoped2025.3
Apply vendor patches for N-central when available; audit and enforce least-privilege file permissions on Agent/Probe installation directories to prevent unauthorized file manipulation by non-admin users.
N-central 2025.3
- Upgrade N-central to version 2025.3 or later to resolve the incorrect default permissions vulnerability
- After upgrading, verify that the Windows Agent and Probe services run with appropriate restricted permissions
- Review user access controls to ensure only authorized administrators have access to agent/probe directories
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10231 — 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-10231 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