dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-46355

HIGH · 7.3 CVSS v3.0 Published 2025-06-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/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
Incorrect default permissions issue in PC Time Tracer prior to 5.2. If exploited, arbitrary code may be executed with SYSTEM privilege on Windows system where the product is running by a local authenticated attacker.

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 confidence

PC Time Tracer prior to version 5.2 ships with incorrect default permissions on its installation directory or related files. This allows a local authenticated attacker to modify executable files or configurations to achieve arbitrary code execution with SYSTEM-level privileges, resulting in complete local privilege escalation.

MitigationUpgrade PC Time Tracer to version 5.2 or later to obtain corrected default permissions, or manually review and restrict permissions on the application directory to prevent unauthorized modification by standard 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
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:R/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 checks

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

  1. Verify PC Time Tracer installation
    Check if PC Time Tracer is installed on the system by looking for its installation directory, commonly under C:\Program Files\PC Time Tracer or C:\Program Files (x86)\PC Time Tracer, or search for the application in Add/Remove Programs.
    Affected if PC Time Tracer is found installed on the system
  2. Identify installed version
    Locate the installed version by checking the program executable properties (right-click the main .exe file in the installation folder, go to Details tab) or by checking the version listed in Add/Remove Programs.
    Affected if The installed version is earlier than 5.2 (e.g., 5.1, 5.0, or any version number below 5.2)
  3. Inspect installation directory permissions
    Right-click the PC Time Tracer installation folder, select Properties, then go to the Security tab. Check which users and groups have permission to Modify or Write to the folder.
    Affected if Standard authenticated users (non-admin users) have Modify or Write permissions to the installation directory or its executable files
  4. Verify executable file permissions
    Within the installation folder, right-click each .exe and .dll file, go to Security tab, and check which users have Write or Modify permissions.
    Affected if Standard users can write or modify any executable files (.exe, .dll) in the PC Time Tracer installation directory

You are affected if PC Time Tracer version 5.2 or later is NOT installed AND standard users have write/modify access to the installation directory or its executable files.

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

Upgrade PC Time Tracer to version 5.2 or later to obtain corrected default permissions, or manually review and restrict permissions on the application directory to prevent unauthorized modification by standard users.

Recommended fix Moderate confidence

PC Time Tracer 5.2

  1. Identify the currently installed version of PC Time Tracer on the affected Windows system
  2. Download PC Time Tracer version 5.2 or later from the official vendor (Keiyo System Co., Ltd.)
  3. Backup any existing PC Time Tracer data and configuration files
  4. Uninstall the current version of PC Time Tracer
  5. Install the new version (5.2 or later)
  6. Verify the installation was successful and the application runs normally
  7. Confirm that the default permissions have been corrected by reviewing file system permissions on the installation directory

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-2025-46355 — 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-46355 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