CVE-2023-47201 is a high severity local privilege escalation in the Trend Micro Apex One plug-in manager, scored 7.8. Weak validation of where commands come from lets someone who already runs code on the machine reach SYSTEM. Apply Apex One SP1 Critical Patch 12526, or the September 2023 monthly patch for the as a service edition.
What's affected
Trend Micro's security bulletin for Apex One, dated 6 November 2023, lists Apex One 2019 (on premises) and Apex One as a Service, both on Windows. The minimum fixed levels are Apex One Service Pack 1 Critical Patch 12526 for on premises installs, and the September 2023 monthly patch (202309) with agent version 14.0.12737 for the as a service edition. Trend Micro advises moving to the latest version if a newer one exists.
This entry is the second plug-in manager issue, CVE-2023-47201. Per the Zero Day Initiative, the flaw is in the Apex One Client Plug-in Service Manager, where insufficient validation of the origin of commands lets a local attacker escalate privileges and run code as SYSTEM. NVD notes it is similar to, but not identical to, CVE-2023-47200.
Dates differ across sources, and it is worth knowing why. The Zero Day Initiative advisory ZDI-23-1613 was released on 14 November 2023, the bulletin is dated 6 November 2023, and the NVD record shows 23 January 2024. These are different events for the same issue, so do not read the NVD date as the date a fix appeared. Severity matches across sources, 7.8 High, with a local vector.
The NVD record was published on 2024-01-23, scores 7.8 (High), and carries the vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Weakness class: CWE-269.
How to check if you're exposed
Apex One agents and the management server are managed from the console, so the check is a version comparison, not a command.
- Open the Apex One management console and review the version of the management server and the agents.
- For on premises installs, confirm that Service Pack 1 Critical Patch 12526 or later is applied, using the readme linked from Trend Micro's bulletin.
- For Apex One as a Service, confirm the agent version is 14.0.12737 or later and the September 2023 monthly patch is in place.
- Sort agents by version and find the machines that are behind, especially shared workstations and servers.
Because the weakness tag differs from its sibling, filter your scanner by CVE rather than by weakness class when you track this.
What to do now
- Read Trend Micro's bulletin and note the minimum patch for your edition.
- Apply the patch to the management server first, then deploy updated agents.
- Find agents that did not update, such as machines that are offline or excluded from policy, and bring them current.
- Test the new self protection behavior. Trend Micro warns that apps not signed by Trend Micro or Microsoft that inject into other processes may be blocked, so add exceptions for trusted tools through the documented process.
- Review who can run code as a standard user on important machines, since every attack in this family starts there.
Why it matters
The record tags this CVE as CWE-269, improper privilege management, where the sibling uses CWE-346, origin validation. Both describe the same observable problem from different angles.
A different tag does not change what to do. The service performs privileged work for a caller whose right to ask has not been properly checked. The vendor patch changes that, and your job is to get it deployed everywhere the agent runs.
The pair of plug-in manager entries is a good reminder that one weakness label does not capture a bug fully. Use the description and the vendor bulletin as your guide. The record's KEV flag is false, so this CVE is not on the CISA Known Exploited Vulnerabilities list.
Quick check
Why does this record use a different weakness tag from CVE-2023-47200?
NVD assigned improper privilege management here and origin validation to its sibling. The vendor bulletin describes both as plug-in manager origin validation errors.
Sources
Last reviewed: 19 October 2026.
