CVE-2025-47865
Trendmicro Apex Central 2019
Raw vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-47865 is a high-severity Undefined Behavior for Input to API (CWE-475) vulnerability in Trendmicro Apex Central. Its CVSS base score is 7.5 (High).
Operationally, ranked in the top 27% of CVEs by exploit likelihood; 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.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
A Local File Inclusion vulnerability affects a widget component in Trend Micro Apex Central versions below 8.0.6955. Tracked as CVE-2025-47865 with a CVSS 3.1 score of 7.5, the flaw stems from improper handling that can be abused to include arbitrary local files and ultimately execute attacker-controlled code on the server.
An authenticated attacker with low privileges can reach the vulnerable widget over the network. Although the attack requires high complexity and no user interaction, successful exploitation grants remote code execution with full impact on confidentiality, integrity, and availability of the Apex Central installation.
Advisories published by Trend Micro and the Zero Day Initiative at the referenced URLs describe the affected widget and the version that resolves the issue. The current EPSS score of 0.0171 with a peak of 0.0190 indicates low and stable exploitation interest since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-18519
Vulnerability Data
A Local File Inclusion vulnerability in a Trend Micro Apex Central widget below version 8.0.6955 could allow an attacker to gain remote code execution on affected installations.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover calls that supply invalid control-parameter values before deployment.
Validating inputs to API control parameters ensures only permitted values are supplied, structurally eliminating the source of undefined behavior.
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.
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.
Security testing can detect undefined behavior from invalid API inputs before deployment.
Secure development lifecycle includes API specification and validation that can prevent undefined behavior from invalid inputs.
Application security requirements can mandate explicit input validation and defined behavior for API parameters.
Secure system architecture principles can require defensive coding that eliminates undefined behavior in APIs.
Secure coding directly addresses avoiding undefined behavior by enforcing defined inputs and error handling in APIs.