dbcve.org
Trend Micro Endpoint EncryptionApplication · Trendmicro

CVE-2025-49218

HIGH · 7.8 CVSS v3.1 Published 2025-06-17
Fix available
A fix is available. Upgrade to 6.0.0.4013 or later.
See remediation →
80/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
A post-auth SQL injection vulnerability in the Trend Micro Endpoint Encryption PolicyServer could allow an attacker to escalate privileges on affected installations. This is similar to, but not identical to CVE-2025-49215. Please note: an attacker must first obtain the ability to execute low-privileged code on the target system to exploit this vulnerability.

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

A post-authentication SQL injection vulnerability exists in the Trend Micro Endpoint Encryption PolicyServer component. An authenticated attacker with the ability to execute low-privileged code on the target system can exploit this flaw to inject malicious SQL queries, potentially escalating privileges to higher permission levels within the PolicyServer database.

MitigationApply the vendor-supplied patch for CVE-2025-49218 when available. Until then, minimize the attack surface by restricting PolicyServer access to only necessary administrative accounts, implementing least-privilege access controls, and monitoring database query logs for anomalous SQL activity.

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
Trend Micro Endpoint EncryptionApplication
Affected:< 6.0.0.4013

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

CVSS:3.1/AV:L/AC:L/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 checks

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

  1. Identify if PolicyServer component is installed
    Locate the Trend Micro Endpoint Encryption installation directory and verify the presence of PolicyServer executables or services. Common locations include Program Files\Trend Micro\Endpoint Encryption or similar. Check for PolicyServer.exe or related service entries in Windows Services.
    Affected if PolicyServer component exists in the environment
  2. Determine installed version of Trend Micro Endpoint Encryption
    Check the version of the installed Endpoint Encryption software. This can typically be found in the program's properties (right-click on executable), in Windows Registry under HKLM\SOFTWARE\TrendMicro\EndpointEncryption, or via the program's About/Help dialog.
    Affected if Installed version is lower than 6.0.0.4013
  3. Verify PolicyServer database accessibility
    Check if the PolicyServer database (commonly SQL Server or SQL Express) is running and exposed. Review network configuration to determine if database ports are listening on external interfaces or if local access is restricted.
    Affected if PolicyServer database is accessible beyond localhost or shared with low-privileged accounts
  4. Audit PolicyServer user accounts
    Review the list of accounts with access to PolicyServer management console and database. Identify any low-privileged accounts that may have been granted limited code execution or database query capabilities.
    Affected if Low-privileged or non-administrative accounts have PolicyServer access

You are affected if Trend Micro Endpoint Encryption with PolicyServer is installed and the version is lower than 6.0.0.4013, especially if low-privileged users have any access to the PolicyServer component.

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 6.0.0.4013 or later
Fixed in 6.0.0.4013
Interim mitigation

Apply the vendor-supplied patch for CVE-2025-49218 when available. Until then, minimize the attack surface by restricting PolicyServer access to only necessary administrative accounts, implementing least-privilege access controls, and monitoring database query logs for anomalous SQL activity.

Recommended fix High confidence

6.0.0.4013

  1. 1. Verify current installed version of Trend Micro Endpoint Encryption PolicyServer
  2. 2. Download the latest version 6.0.0.4013 or later from the Trend Micro official download center
  3. 3. Follow Trend Micro's standard upgrade procedure for Endpoint Encryption PolicyServer
  4. 4. Verify the upgrade was successful by checking the PolicyServer version
  5. 5. Test that the PolicyServer functionality operates normally after upgrade

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

Fix this in Trend Micro Endpoint Encryption Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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