CVE-2025-53947
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 · uneditedA local attacker with low privileges on the Windows system where the software is installed can exploit this vulnerability to corrupt sensitive data. A data folder is created with very weak privileges, allowing any user logged into the Windows system to modify its content.
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 confidenceA local attacker with low privileges on a Windows system can exploit weak folder permissions to corrupt sensitive data. The software creates a data folder with overly permissive access controls, allowing any logged-in user to modify its contents.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/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 the application's data folderIdentify where the vulnerable software stores its data. Common locations include ProgramData, AppData, or a custom data directory under the installation folder. Check installation documentation or monitor folder creation during software first run.Affected if The data folder exists and contains sensitive files that could be modified by any user.
-
Review folder ACL permissionsRight-click the data folder, go to Properties > Security tab. Click 'Advanced' to view the effective permissions. Check the Access Control Entries (ACEs) listed under the Permission entries.Affected if Any user account (especially 'Users' group or 'Everyone') has Write, Modify, or Full Control permissions on the folder.
-
Verify Everyone or Users group write accessIn the Advanced Security Settings, examine if 'Everyone', 'Users', or 'Authenticated Users' principal has permissions beyond Read & Execute or Read. Look specifically for Allow entries with Write, Modify, or Full Control.Affected if The Everyone group or Users group has Write, Modify, or Full Control permissions granted.
-
Check for weak inherited permissionsIn the Advanced Security Settings, verify if permissions are inherited from a parent folder with overly broad access. Look for ACEs that were not explicitly set but inherited from parent directories.Affected if Permissions are inherited from a parent folder that grants broad write access to regular users.
If the data folder grants Write, Modify, or Full Control permissions to the Users group, Everyone, or other low-privilege accounts, the environment is affected by this vulnerability.
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 dataRestrict permissions on the data folder to limit access to only the service account or administrator, and ensure folders are created with secure default permissions (e.g., using explicit ACLs) during installation or first run.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53947 — 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-53947 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