Skip to main content
VulnerabilityPublished Updated

CVE-2023-29505: Zoho ManageEngine Network Configuration Manager

Source CVE Database V5

0

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 64% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AC:L/AV:N/A:N/C:L/I:N/PR:N/S:U/UI:R

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Aug 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
n/a n/aAffected
  • =12.6.165
Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should first verify if Zoho has released patches or updates addressing CVE-2023-29505 and apply them promptly. In the absence of patches, administrators should restrict access to the Network Configuration Manager WebSocket endpoint by implementing strict network segmentation and firewall rules to limit connections only to trusted IP addresses and internal networks. Enforce the use of secure authentication mechanisms and session management best practices to reduce the risk of session hijacking. Additionally, configure web application firewalls (WAFs) to detect and block suspicious WebSocket traffic and cross-origin requests. Educate users about the risks of phishing and social engineering attacks that could trigger this vulnerability. Monitoring WebSocket traffic for anomalies and reviewing logs for unauthorized access attempts can help detect exploitation attempts early. Finally, consider disabling WebSocket features if not essential or deploying reverse proxies that validate origin headers and enforce strict CORS policies to prevent cross-site hijacking.

Description

An issue was discovered in Zoho ManageEngine Network Configuration Manager 12.6.165. The WebSocket endpoint allows Cross-site WebSocket hijacking.

References

Community reviews

Loading reviews…