dbcve.org
Apex CentralApplication · Trendmicro

CVE-2025-47867

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Local File Inclusion vulnerability in a Trend Micro Apex Central widget in versions below 8.0.6955 could allow an attacker to include arbitrary files to execute as PHP code and lead to remote code execution on affected installations.

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 · high confidence

A Local File Inclusion vulnerability exists in a Trend Micro Apex Central widget component in versions prior to 8.0.6955. The flaw allows unauthenticated attackers to include arbitrary files from the host system, which can then be executed as PHP code leading to remote code execution.

MitigationUpgrade Apex Central to version 8.0.6955 or later. As an interim measure, deploy WAF rules to block directory traversal patterns (../) in widget parameter inputs.

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
Apex CentralApplication
Affected:= 2019

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm Apex Central installation
    Locate the Apex Central installation directory (commonly C:\Program Files\Trend Micro\Apex Central or /opt/trendmicro/apexcentral) or check for the 'Trend Micro Apex Central' Windows service.
    Affected if Apex Central is not found on the system.
  2. Identify installed version
    Check the version by viewing the management console home page, or locate a version file in the installation directory (such as version.txt, build.dat, or in the web application's footer).
    Affected if The version is below 8.0.6955 (including version 2019 releases).
  3. Verify widget component is present
    Access the Apex Central management console and navigate to the widget dashboard or check for the presence of widget-related PHP files in the web root (such as /widget/ or /widgets/ directories).
    Affected if The widget component is installed and accessible.
  4. Test widget accessibility
    Attempt to access the widget functionality via the web interface or directly via HTTP requests to widget-related endpoints (e.g., /widget/*.php).
    Affected if The widget interface is reachable without authentication or via valid authentication.

The environment is affected if Trend Micro Apex Central is installed with a version below 8.0.6955 and the widget component is accessible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Apex Central to version 8.0.6955 or later. As an interim measure, deploy WAF rules to block directory traversal patterns (../) in widget parameter inputs.

Recommended fix High confidence

Apex Central 8.0.6955

  1. Identify the current version of Trend Micro Apex Central by accessing the product console or using the built-in version check
  2. Download the fixed version 8.0.6955 from the official Trend Micro download center or contact Trend Micro support
  3. Review the upgrade guide and release notes for Apex Central 8.0.6955
  4. Create a complete backup of the current Apex Central installation including database and configuration files
  5. Schedule a maintenance window to minimize business impact
  6. Execute the upgrade following the official installation/upgrade documentation
  7. Verify the upgrade was successful by checking the version number in the product console
  8. Validate that the vulnerability is remediated by confirming the LFI vulnerability in the widget component is no longer exploitable
Caveat Review release notes for any configuration or feature changes between current version and 8.0.6955; test in non-production environment first

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

Fix this in Apex Central Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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