dbcve.org
Trend Micro Endpoint EncryptionApplication · Trendmicro

CVE-2025-49211

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 SQL injection vulnerability in the Trend Micro Endpoint Encryption PolicyServer could allow an attacker to escalate privileges on affected installations. 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

SQL injection vulnerability in Trend Micro Endpoint Encryption PolicyServer allows authenticated attackers to escalate privileges by injecting malicious SQL queries through insufficiently sanitized input in the PolicyServer component. The attacker must first obtain low-privileged code execution on the target system before exploiting this vulnerability.

MitigationApply vendor-provided patches for Trend Micro Endpoint Encryption PolicyServer. If patches are unavailable, implement input validation and parameterized queries in the PolicyServer SQL interactions as an interim measure.

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 Trend Micro Endpoint Encryption version
    Check the installed version of Trend Micro Endpoint Encryption on the system. This can typically be found in Add/Remove Programs, the program's About/Help menu, or via command line tools provided by Trend Micro. Compare the version number to the affected range.
    Affected if The installed version is lower than 6.0.0.4013 (e.g., 6.0.0.4000, 5.x.x, etc.)
  2. Verify PolicyServer component installation
    Determine whether the PolicyServer component of Trend Micro Endpoint Encryption is installed on the system. This component is required for the SQL injection vulnerability to be exploitable.
    Affected if PolicyServer is installed and running as part of the Endpoint Encryption deployment.
  3. Check PolicyServer network exposure
    Review the PolicyServer configuration to determine if it is accessible over the network or bound to an interface that could be reached by an attacker with low-privileged code execution.
    Affected if PolicyServer is network-accessible from contexts where an attacker has obtained low-privileged code execution.
  4. Confirm authenticated access context
    Assess whether the PolicyServer accepts authentication from the endpoint agents or management consoles, as the SQL injection requires an authenticated attacker.
    Affected if PolicyServer is configured to accept authenticated connections from endpoints or administrators.

A system is affected if it runs Trend Micro Endpoint Encryption with PolicyServer installed and the installed version is below 6.0.0.4013, combined with the presence of an authenticated attacker context.

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 vendor-provided patches for Trend Micro Endpoint Encryption PolicyServer. If patches are unavailable, implement input validation and parameterized queries in the PolicyServer SQL interactions as an interim measure.

Recommended fix High confidence

6.0.0.4013 or later

  1. 1. Identify the current version of Trend Micro Endpoint Encryption PolicyServer by accessing the PolicyServer management console or checking the installed software version
  2. 2. Verify the version is below 6.0.0.4013 - if already at or above this version, no action is needed
  3. 3. Download the updated Trend Micro Endpoint Encryption version 6.0.0.4013 or later from the Trend Micro Success Portal at success.trendmicro.com or contact Trend Micro support
  4. 4. Review the upgrade documentation and release notes for any specific prerequisites or migration considerations
  5. 5. Create a complete backup of the PolicyServer database and configuration settings before upgrading
  6. 6. Test the upgrade in a non-production environment first to ensure compatibility with existing systems and configurations
  7. 7. Schedule a maintenance window as the upgrade may require service downtime
  8. 8. Apply the upgrade to the PolicyServer following Trend Micro's official upgrade procedures
Caveat Review release notes for any compatibility changes or migration requirements specific to your environment

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

Fix this in Trend Micro Endpoint Encryption Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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