CVE-2025-25011
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 confidenceA local attacker with standard user access can exploit insecure directory permissions to manipulate files through an uncontrolled search path element. This allows moving or deleting arbitrary files on the system, which can be chained to achieve SYSTEM-level 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
- 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 system PATH environmentRun 'echo $PATH' on Linux/macOS or 'echo %PATH%' in Windows Command Prompt to list all directories in the search pathAffected if Any directory in PATH is writable by a standard (non-privileged) user
-
Check write permissions on PATH directories (Linux/macOS)For each directory in PATH, run 'ls -ld <directory>' and check the permission bits. Specifically examine the 'w' permission for the 'other' or 'group' categoryAffected if Any PATH directory shows write permission for non-owner users (permissions like 'drwxrwxrwx' or 'drwxrwxrwx' where others have 'w')
-
Check write permissions on PATH directories (Windows)Use 'icacls <directory>' for each PATH directory to inspect permissions. Look for entries granting Write/Modify to 'Users' or 'Authenticated Users' groupAffected if Any PATH directory grants Write or Modify permissions to standard users or Everyone
-
Audit directories for unsafe ownershipRun 'ls -ln <directory>' to check if PATH directories are owned by non-root users, or on Windows use 'icacls <directory>' to check ownerAffected if A PATH directory is owned by a standard user or a writable directory exists in the path that is not owned by a privileged account
-
Search for world-writable directories in system pathsOn Linux/macOS, run 'find /usr/bin /usr/sbin /bin /sbin /usr/local/bin -type d -perm -002 2>/dev/null' to find world-writable system directoriesAffected if Any system binary directory (used in search paths) is world-writable
The environment is affected if any directory in the system PATH is writable by standard (non-privileged) users, allowing path manipulation 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.
From vendor dataRestrict directory permissions to prevent unauthorized modification of directories in the search path, ensuring only privileged users can write to these locations.
- 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-25011 — 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-25011 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