CVE-2023-45722: HCL Software DRYiCE MyXalytics · Path Traversal
Affects HCL Software DRYiCE MyXalyticsSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| HCL Software DRYiCE MyXalytics | Affected
| Fixed in– |
AI-suggested
2) Implement strict input validation and sanitization on all user-supplied path parameters to prevent traversal sequences. 3) Employ runtime application self-protection (RASP) or web application firewalls (WAFs) configured to detect and block path traversal attempts targeting MyXalytics endpoints. 4) Restrict access to the MyXalytics application to trusted networks and authenticated users with the minimum necessary privileges, as the vulnerability requires low privileges but still authentication. 5) Conduct regular security audits and penetration testing focused on file path handling and directory traversal vulnerabilities. 6) Monitor application logs for suspicious access patterns indicative of traversal attempts. 7) Consider deploying file integrity monitoring on critical directories to detect unauthorized file access or changes. These measures, combined with timely patching, will reduce the risk of exploitation and limit potential damage.
Description
HCL DRYiCE MyXalytics is impacted by path traversal arbitrary file read vulnerability because it uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory. The product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Potential exploits can completely disrupt or take over the application.