Cyber Resilience

CVE-2023-52091

Trendmicro Apex One ≤ 14.0.12849

Published
23 January 2024
Modified
20 June 2025
Patch / advisory
View advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0031 23th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2023-52091 is a high-severity Link Following (CWE-59) vulnerability in Trendmicro Apex One. Its CVSS base score is 7.8 (High).

Operationally, ranked at the 23th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

An anti-spyware engine link following vulnerability in Trend Micro Apex One could allow a local attacker to escalate privileges on affected installations. Please note: an attacker must first obtain the ability to execute low-privileged code on the target system in…

more

order to exploit this vulnerability.

CWE(s)
CWE-59

Related Threats

CVEs Like This One

CVE-2023-52094Same product: Trendmicro Apex One
CVE-2023-52090Same product: Trendmicro Apex One
CVE-2023-47192Same product: Trendmicro Apex One
CVE-2023-52092Same product: Trendmicro Apex One
CVE-2024-36305Same product: Trendmicro Apex One
CVE-2025-71212Same product: Trendmicro Apex One
CVE-2024-52050Same product: Trendmicro Apex One
CVE-2024-36306Same product: Trendmicro Apex One
CVE-2025-49156Same product: Trendmicro Apex One
CVE-2025-49157Same product: Trendmicro Apex One

Affected Assets

trendmicro
apex one
2019 · ≤ 14.0.12849

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)
  • V15.4.2

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

Secure SDLC practices directly require code to validate paths and avoid unsafe link following.

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
detects

Security testing can detect link-following flaws before release.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC practices can mandate link-resolution checks and canonicalization before file access.

A.8.26 Application security requirements partial match
prevents

Application security requirements can explicitly require safe handling of symbolic links and path traversal.

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

Secure architecture principles include input validation and safe file-access design patterns.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly address canonicalization and symlink attacks during implementation.

A.8.3 Information access restriction none match
none

Access-control rules can limit which files are reachable, reducing exposure to malicious links.

References