dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2026-0539

HIGH · 8.5 CVSS v4.0 Published 2026-04-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Zero-click

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
Incorrect Default Permissions in pcvisit service binary on Windows allows a low-privileged local attacker to escalate their privileges by overwriting the service binary with arbitrary contents. This service binary is automatically launched with NT\SYSTEM privileges on boot. This issue affects all versions after 22.6.22.1329 and was fixed in 25.12.3.1745.

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

The pcvisit Windows service binary has incorrect default file permissions allowing a low-privileged local user to overwrite the binary with malicious code. Since the service executes with NT\SYSTEM privileges on system boot, an attacker can achieve privilege escalation by replacing the binary and triggering a service restart.

MitigationUpdate pcvisit to version 25.12.3.1745 or later. Alternatively, verify and restrict file permissions on the service binary to prevent unauthorized modification by non-admin users.

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:N/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 checks

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

  1. Locate pcvisit service and its binary path
    Open Services console (services.msc), find the pcvisit service, right-click and select Properties, note the 'Path to executable' field. Alternatively, run: sc qc pcvisit
    Affected if Service exists and binary path is identified
  2. Identify installed pcvisit version
    Check version of the executable file located in the previous step. In File Explorer, right-click the binary, select Properties, and view the Details tab for Product Version. Alternatively, right-click the file, select Properties, then check the Version tab.
    Affected if Installed version is lower than 25.12.3.1745 (the fixed version)
  3. Verify file permissions on the service binary
    Right-click the service binary file, select Properties, go to the Security tab, and check the permissions for Users or non-admin groups. Alternatively, run: icacls "C:\path\to\pcvisit.exe" (replace with actual path)
    Affected if Users or low-privileged accounts have Write or Full Control permissions on the binary, allowing them to modify or replace it
  4. Confirm service runs with elevated privileges
    In Services console, check the 'Log On As' setting for the pcvisit service. It is typically set to run as NT AUTHORITY\SYSTEM or Local System.
    Affected if Service is configured to run as SYSTEM or Local System account

A user is affected if pcvisit is installed with a version below 25.12.3.1745 AND the service binary is writable by low-privileged users AND the service runs as SYSTEM.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update pcvisit to version 25.12.3.1745 or later. Alternatively, verify and restrict file permissions on the service binary to prevent unauthorized modification by non-admin users.

Recommended fix High confidence

Upgrade to pcvisit version 25.12.3.1745

  1. 1. Identify all systems with pcvisit software installed
  2. 2. Check current installed version (likely via Add/Remove Programs or the application's About/Help section)
  3. 3. If version is after 22.6.22.1329 and before 25.12.3.1745, the system is vulnerable
  4. 4. Download the fixed version 25.12.3.1745 from the official vendor (pcvisit.de) or trusted distribution channel
  5. 5. Before upgrading, create a backup of the current installation and any critical data
  6. 6. Uninstall the current vulnerable version or run the installer to upgrade to 25.12.3.1745
  7. 7. After installation, verify the new version is 25.12.3.1745
  8. 8. Restart the system to ensure the service loads the new binary with correct permissions

Generated from the published advisory — verify against the referenced sources before acting.

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

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0539 — 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-2026-0539 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