CVE-2025-11567
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 · uneditedCWE-276: Incorrect Default Permissions vulnerability exists that could cause elevated system access when the target installation folder is not properly secured.
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 confidenceCWE-276: Incorrect Default Permissions vulnerability where the target installation folder has overly permissive access controls, allowing unprivileged users to modify or replace executable files or configurations within the installation directory, potentially leading to elevated system privileges.
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
- Local
- Complexity
- Low
- Privileges
- Low
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 the installation directoryIdentify the installation folder for the target application. This is typically found in Program Files, Program Files (x86), or a custom application path noted during initial installation.Affected if The specific application folder cannot be located for further permission checks
-
Review folder-level permissionsRight-click the installation folder, go to Properties > Security tab. Examine the permissions for groups such as Everyone, Users, Authenticated Users, or custom user groups. Check if any of these have Write or Modify permissions granted.Affected if Non-admin users or groups like 'Users' or 'Everyone' are granted Write or Modify access to the installation folder
-
Inspect executable file permissionsWithin the installation folder, locate .exe and .dll files. Right-click each file, go to Properties > Security, and verify which users or groups have Write permission on these files.Affected if Non-admin users can write or modify executable (.exe) or dynamic library (.dll) files in the installation directory
-
Check configuration file permissionsLocate configuration files in the installation folder (e.g., .ini, .conf, .xml, .json, .config files). Right-click each, go to Properties > Security, and verify write permissions for non-admin users.Affected if Non-admin users have Write or Modify access to configuration files that the application reads at runtime
-
Verify service account restrictionsIf the application runs as a Windows service, confirm using Services.msc which account runs the service. Check if that service account has excessive permissions beyond what is required.Affected if The service account running the application has overly broad permissions on the installation directory
A user is affected if unprivileged (non-admin) users or groups have Write or Modify permissions on executable files, DLLs, or configuration files within the installation directory, allowing potential 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.
From vendor dataConfigure restrictive NTFS/folder permissions on the installation directory following the principle of least privilege, removing unnecessary write/modify access for non-admin users and ensuring only authorized service accounts have required access.
- Consultation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11567 — 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-11567 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