CVE-2025-0712
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 uncontrolled search path element vulnerability can lead to local privilege Escalation (LPE) via Insecure Directory Permissions. The vulnerability arises from improper handling of directory permissions. An attacker with local access may exploit this flaw to move and delete arbitrary files, potentially gaining SYSTEM privileges.
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 stemming from insecure directory permissions. An attacker with local access can manipulate directories in the application's search path to move or delete arbitrary files, potentially elevating privileges to SYSTEM level.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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 the affected applicationDetermine which application on your system uses directories in its search path that could be manipulated. Since no specific product is listed in the CVE, identify applications that load executables or modules from user-writable locations.Affected if The application uses directories in its PATH or module search path that are writable by low-privilege users.
-
Locate directories in the application search pathFor the identified application, examine its configuration, environment variables (PATH), and runtime settings to list all directories it searches for executables, libraries, or modules.Affected if The application references directories that exist in shared or writable locations.
-
Inspect permissions on search path directoriesUse operating system tools to check ACLs or mode bits on each directory in the search path. On Windows, use icacls or AccessChk. On Linux/Unix, use ls -ld or namei -l.Affected if Low-privilege users have write, modify, or delete permissions on any directory in the search path.
-
Verify if directories can be manipulatedTest whether a low-privilege user account can rename, move, delete, or replace files within the search path directories. Attempt to create symbolic links or hard links if supported.Affected if A non-privileged user can alter contents or structure of directories used in the search path.
-
Check for unsafe PATH or module load configurationReview environment variables and application configuration for entries that point to world-writable directories, temp folders, or user-controlled locations.Affected if The search path includes directories like temp, public, or shared folders accessible to other users.
You are affected if any directory in the application's search path grants low-privilege users the ability to manipulate files or directory structure, allowing privilege escalation to SYSTEM level.
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 dataFix directory permission handling to ensure proper access controls on directories used in the search path; restrict local user permissions to prevent manipulation of executable locations.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0712 — 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-0712 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