Authenticated code execution via unvalidated PHP include
Published Jun 17, 2025 · Updated Feb 26, 2026
Local file inclusion in Trend Micro Apex Central 2019 before build 6955 allows remote authenticated users to execute code as IUSR. The getBlock function passes user-supplied data to a PHP include operation without proper validation, allowing a local file to be interpreted as PHP code. Exploitation requires authentication and use with other vulnerabilities; successful execution runs in the IUSR context.
Summary
What happened
Local file inclusion in Trend Micro Apex Central 2019 before build 6955 allows remote authenticated users to execute code as IUSR. The getBlock function passes user-supplied data to a PHP include operation without proper validation, allowing a local file to be interpreted as PHP code. Exploitation requires authentication and use with other vulnerabilities; successful execution runs in the IUSR context.
The record
- CVE
- CVE-2025-47867
- Published
- Jun 17, 2025
- Updated
- Feb 26, 2026
- Vendor
- Trend Micro
- Product
- Apex Central
- Classifications
- CWE-74, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 17, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=8.0 <8.0.6955
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo