dbcve.org
Password ManagerApplication · Trendmicro

CVE-2025-48443

MEDIUM · 6.6 CVSS v3.1 Published 2025-06-17
Fix available
A fix is available. Upgrade to 5.8.0.1330 or later.
See remediation →
66/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
Trend Micro Password Manager (Consumer) version 5.0.0.1266 and below is vulnerable to a Link Following Local Privilege Escalation Vulnerability that could allow a local attacker to leverage this vulnerability to delete files in the context of an administrator when the administrator installs Trend Micro Password Manager.

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

This is a link following (symlink attack) vulnerability in Trend Micro Password Manager's installer that allows a local attacker to delete files with administrator privileges during the installation process. The vulnerability stems from improper handling of symbolic links, enabling privilege escalation from a low-privilege context to administrator-level file operations.

MitigationApply vendor-supplied patches once available; until then, restrict physical and local access to the system during software installation and monitor installation directories for suspicious symbolic link creation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Password ManagerApplication
Affected:< 5.8.0.1330

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
None
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/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 Trend Micro Password Manager is installed
    Check the installed programs list on the system (Windows: Programs and Features, or via registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\) for Trendmicro Password Manager entry
    Affected if The product is listed as installed on the system
  2. Determine the installed version
    Locate the installed version information - typically found in the uninstall registry entry, or check the main executable properties if the installation directory is known
    Affected if The version shown is lower than 5.8.0.1330 or the version cannot be determined (older installation)
  3. Compare against affected version range
    Compare your installed version against the known vulnerable range: any version before 5.8.0.1330 is affected
    Affected if The installed version is any release prior to 5.8.0.1330
  4. Identify installation directories
    Locate the default installation paths (typically C:\Program Files\Trend Micro\ or C:\Program Files (x86)\Trend Micro\) and check for the Password Manager component folders
    Affected if Installation directories exist and contain pre-5.8.0.1330 version files
  5. Check for recent installation activity
    Review installation logs, temporary directories, or recent modification dates on the Trend Micro Password Manager installation folders
    Affected if Installation occurred recently or files were modified within the vulnerable version timeline

The environment is affected if Trend Micro Password Manager is installed with any version prior to 5.8.0.1330.

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
Upgrade available Upgrade to 5.8.0.1330 or later
Fixed in 5.8.0.1330
Interim mitigation

Apply vendor-supplied patches once available; until then, restrict physical and local access to the system during software installation and monitor installation directories for suspicious symbolic link creation.

Recommended fix High confidence

5.8.0.1330 or later

  1. 1. Close any running instances of Trend Micro Password Manager
  2. 2. Download the latest version of Trend Micro Password Manager from the official Trend Micro support center (helpcenter.trendmicro.com)
  3. 3. Run the installer and follow the on-screen prompts to complete the upgrade
  4. 4. After installation, restart your computer to ensure all components are properly updated
  5. 5. Verify the installed version is 5.8.0.1330 or higher

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

Fix this in Password Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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