Cyber Resilience

CVE-2025-47866

Trendmicro Apex Central 2019

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

Summary

CVE-2025-47866 is a medium-severity Undefined Behavior for Input to API (CWE-475) vulnerability in Trendmicro Apex Central. Its CVSS base score is 4.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 16th 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)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

An unrestricted file upload vulnerability in a Trend Micro Apex Central widget below version 8.0.6955 could allow an attacker to upload arbitrary files on affected installations.

CWE(s)
CWE-475CWE-434

Related Threats

MITRE ATT&CK Enterprise Techniques

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.
attack.mitre.org →
T1505 Server Software Component Persistence
Adversaries may abuse legitimate extensible development features of servers to establish persistent access to systems.
attack.mitre.org →
T1505.003 Web Shell Persistence
Adversaries may backdoor web servers with web shells to establish persistent access to systems.
attack.mitre.org →
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
T1105 Ingress Tool Transfer Command And Control
Adversaries may transfer tools or other files from an external system into a compromised environment.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-47865Same product: Microsoft Windows
CVE-2025-30679Same product: Microsoft Windows
CVE-2025-30680Same product: Microsoft Windows
CVE-2025-30678Same product: Microsoft Windows
CVE-2025-47867Same product: Microsoft Windows
CVE-2025-49220Same product: Microsoft Windows
CVE-2025-49219Same product: Microsoft Windows
CVE-2025-69260Same product: Microsoft Windows
CVE-2025-69259Same product: Microsoft Windows
CVE-2025-69258Same product: Microsoft Windows

Affected Assets

trendmicro
apex central
2019

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)
  • V5.1.1

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover calls that supply invalid control-parameter values before deployment.

SI-10 Information Input Validation good match

Validating inputs to API control parameters ensures only permitted values are supplied, structurally eliminating the source of undefined behavior.

SI-3 Malicious Code Protection good match

Malicious-code protection at entry points blocks dangerous file types from being accepted and executed.

CM-7 Least Functionality partial match

Least functionality restricts the file types and automatic processing capabilities the system will accept.

SC-18 Mobile Code partial match

Mobile-code controls define, authorize, and block unacceptable uploaded code before automatic processing occurs.

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-05 mostly match
prevents

Restricting execution of unauthorized software directly blocks dangerous uploaded files from running.

PR.PS-06 mostly match
prevents

Secure SDLC practices (coding standards, reviews, testing) directly prevent undefined behavior from invalid API inputs.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover and record this class of API-related weakness.

PR.PS-01 partial match
prevents

Hardened configuration baselines can enforce allowed file types and processing rules.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect undefined behavior from invalid API inputs before deployment.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes API specification and validation that can prevent undefined behavior from invalid inputs.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate explicit input validation and defined behavior for API parameters.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture principles can require defensive coding that eliminates undefined behavior in APIs.

A.8.28 Secure coding partial match
prevents

Secure coding directly addresses avoiding undefined behavior by enforcing defined inputs and error handling in APIs.

A.8.30 Outsourced development partial match
prevents

Mandated testing for malicious content and known vulnerabilities reduces the likelihood that an outsourced component will contain or accept dangerous file types that could later be uploaded or executed.

References