dbcve.org
Apex OneApplication · Trendmicro

CVE-2024-52047

HIGH · 8.8 CVSS v3.1 Published 2024-12-31
Fix available
A fix is available. Upgrade to 14.0.13139 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 widget local file inclusion vulnerability in Trend Micro Apex One could allow a remote attacker to execute arbitrary code on affected installations. Please note: an attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability.

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

A local file inclusion (LFI) vulnerability in Trend Micro Apex One's widget component allows reading arbitrary files from the server filesystem. While the CVSS is 8.8 HIGH, exploitation requires the attacker to first obtain low-privileged code execution on the target system, then leverage the LFI for privilege escalation, reading sensitive configuration files, or accessing credential/data files to further compromise the system.

MitigationApply the vendor security patch or upgrade to a fixed version of Apex One when released. Until then, restrict network access to the Apex One management console to trusted IPs only and monitor for signs of initial compromise that could enable this secondary attack vector.

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 OneApplication
Affected:< 14.0.13139= 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify Apex One installation exists
    Locate Apex One installation directories - common paths include C:\Program Files\Trend Micro\Apex One or check Windows Services for 'Apex One' services
    Affected if Apex One software is found on the system
  2. Identify installed Apex One version
    Open the Apex One management console and navigate to Updates > Product Licensing, or check the registry key HKLM\SOFTWARE\TrendMicro\Apex One\CurrentVersion, or run 'officescan.exe version' from the installation directory
    Affected if Version number is lower than 14.0.13139 or matches version 2019 (year-based release)
  3. Confirm web management console accessibility
    Access the Apex One web console URL (typically https://localhost:4343 or the configured management port) and verify it responds
    Affected if Web console is accessible - the widget component LFI can only be exploited through this interface
  4. Check for signs of prior low-privileged access
    Review Windows Security event logs for unexpected user logins, new service accounts, or process creation under non-admin users since this LFI requires initial low-privileged code execution first
    Affected if Evidence exists of unauthorized low-privileged access that could have been used to reach the LFI

You are affected if Apex One is installed with version below 14.0.13139 (or is the 2019 release) AND the web management console is accessible to the attacker.

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
Upgrade available Upgrade to 14.0.13139 or later
Fixed in 14.0.13139
Interim mitigation

Apply the vendor security patch or upgrade to a fixed version of Apex One when released. Until then, restrict network access to the Apex One management console to trusted IPs only and monitor for signs of initial compromise that could enable this secondary attack vector.

Recommended fix High confidence

Apex One version 14.0.13139 or later

  1. 1. Check the current version of Apex One by navigating to the Apex One web console > Help > About, or by checking the version information in the installation directory.
  2. 2. Confirm the version is either below 14.0.13139 or is version 2019, which are affected by this vulnerability.
  3. 3. Download Apex One version 14.0.13139 or later from the Trend Micro Download Center at success.trendmicro.com or the official Trend Micro support portal.
  4. 4. Review Trend Micro's upgrade documentation and ensure system requirements are met for the new version.
  5. 5. Create a complete backup of the Apex One database and configuration settings.
  6. 6. Schedule a maintenance window to minimize business impact.
  7. 7. Stop all Apex One services before beginning the upgrade process.
  8. 8. Run the upgrade installer with appropriate administrative privileges.

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

Fix this in Apex One Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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