Cyber Resilience

CVE-2025-49215

SQLi in Trendmicro Trend Micro Endpoint Encryption ≤ 6.0.0.4013

Published
17 June 2025
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0028 20th percentile
Risk Priority 63 floored blend · peak EPSS

Summary

CVE-2025-49215 is a high-severity Use of Inherently Dangerous Function (CWE-242) vulnerability in Trendmicro Trend Micro Endpoint Encryption. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 20th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A post-auth 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…

more

exploit this vulnerability.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-23459Same product: Microsoft Windows
CVE-2019-13373Same product: Microsoft Windows
CVE-2023-22268Same product: Microsoft Windows
CVE-2023-22275Same product: Microsoft Windows
CVE-2023-3864Same product: Microsoft Windows
CVE-2023-25839Same product: Microsoft Windows
CVE-2024-9194Same product: Microsoft Windows
CVE-2017-14078Same vendor: Trendmicro
CVE-2024-39753Same vendor: Trendmicro
CVE-2024-46902Same vendor: Trendmicro

Affected Assets

trendmicro
trend micro endpoint encryption
≤ 6.0.0.4013

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V6.2.5

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and code analysis can locate calls to known dangerous functions after they have been written.

Input validation directly stops untrusted data from reaching SQL query construction without neutralization.

Documented development standards and tools can explicitly prohibit or replace inherently dangerous functions.

An SDLC that incorporates security can embed rules against unsafe functions in coding and review phases.

Engineering principles can mandate avoidance of unsafe library functions during design and coding.

System monitoring can identify attempted SQLi exploitation via anomalous queries after the weakness exists.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prohibit or replace inherently dangerous functions via coding standards, reviews, and tooling.

PR.AT-02 partial match
prevents

Training raises developer awareness of SQLi risks and can reduce introduction likelihood (partial) but removes none of the actual coding flaw's risk by itself since technical neutralization is still required.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can surface calls to unsafe functions but does not prevent their introduction.

prevents

Early warnings and shared best-practice information help organizations apply the latest remediation techniques against SQL-injection vulnerabilities.

prevents

Threat-intelligence feeds that surface new SQL-injection campaigns enable rapid updates to query-construction defenses and detection signatures before exploitation occurs.

prevents

Secure SDLC processes include code review and static analysis that can detect dangerous function usage.

prevents

Secure coding standards explicitly ban or restrict inherently dangerous functions.

none

Controlled software installation reduces exposure to unsafe third-party code containing dangerous functions.

References