dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-13905

HIGH · 7.0 CVSS v4.0 Published 2026-01-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated

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 · unedited
CWE-276: Incorrect Default Permissions vulnerability exists that could cause privilege escalation through the reverse shell when one or more executable service binaries are modified in the installation folder by a local user with normal privilege upon service restart.

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 confidence

This is a CWE-276 (Incorrect Default Permissions) vulnerability where service executable binaries in the installation folder have overly permissive default permissions, allowing a local unprivileged user to modify them. When the service restarts, the modified binary executes with elevated (service) privileges, enabling privilege escalation via reverse shell.

MitigationFix the default file permissions on affected service binaries to restrict write access to administrators/root only, ensuring unprivileged users cannot modify executable files in the installation directory.

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
P
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate service executable binaries in the installation folder
    Identify all executable files (.exe, .dll, .bin, etc.) in the application's installation directory. On Linux/Unix, use: find /path/to/install -type f \( -perm -u+x -o -name "*.exe" \). On Windows, check the installation folder for service-related executables.
    Affected if Service binaries exist in the installation folder and are accessible to unprivileged users.
  2. Check file permissions on identified binaries
    Use 'ls -la' (Linux/Unix) or 'icacls' (Windows) to inspect permissions. Look for permissions granting write access to 'Everyone', 'Users', or non-admin groups. Example Linux: ls -la /path/to/servicebinary. Example Windows: icacls C:\path\to\service.exe
    Affected if Binaries are writable by unprivileged users (world-writable, group-writable by Users group, or lacking restrictive ACLs).
  3. Identify services configured to run the binaries
    On Linux/Unix: grep -r 'exec' /etc/init.d/ or systemctl list-units --type=service. On Windows: sc query or check services.msc to find services pointing to binaries in the installation folder.
    Affected if Any service is configured to execute a binary from this installation folder.
  4. Verify service runs with elevated privileges
    Check the service account or user context. Linux/Unix: systemctl show <servicename> | grep User or ps -ef | grep <servicename>. Windows: sc qc <servicename> and note the BINARY_PATH_NAME, or check service properties for 'Log on as'.
    Affected if The service runs as root, SYSTEM, or another privileged account.
  5. Confirm unprivileged user can modify the binary
    As a test, attempt to write to the binary file using a low-privilege account, or analyze permission inheritance. If the file is owned by root but world-writable, or group-writable by a group the test user belongs to, modification is possible.
    Affected if An unprivileged user can successfully modify (write/overwrite) the service binary file.

You are affected if service executable binaries in the installation folder are writable by unprivileged users and those services run with elevated privileges, allowing potential privilege escalation upon service restart.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Fix the default file permissions on affected service binaries to restrict write access to administrators/root only, ensuring unprivileged users cannot modify executable files in the installation directory.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13905 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13905 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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