CVE-2021-27774: HCL Digital Experience · Information Exposure Through an Error Message
Affects HCL Digital ExperienceSource CVE Database V5
Not known to be exploited · CVSS 3.1 Low.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 22 Sep 2022
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 HCL Digital Experience | Affected
| Fixed in– |
AI-suggested
To mitigate the risk posed by CVE-2021-27774, European organizations should implement the following specific measures: 1) Review and sanitize all error messages generated by HCL Digital Experience to ensure that user input is not reflected back in responses. This may involve customizing error handling routines or applying vendor-provided patches or updates once available. 2) Implement strict input validation and output encoding to prevent injection of malicious content into error messages. 3) Configure web application firewalls (WAFs) to detect and block suspicious requests that attempt to exploit error message reflection. 4) Educate employees and users about phishing risks, emphasizing awareness of suspicious URLs and error messages that may be crafted to appear legitimate. 5) Monitor logs for unusual error message patterns or repeated triggering of error responses that include user input, which could indicate attempted exploitation. 6) Engage with HCL Software support to obtain any available patches or recommended configuration changes addressing this vulnerability. 7) Conduct regular security assessments and penetration testing focused on error handling and information disclosure to proactively identify and remediate similar issues.
Description
User input included in error response, which could be used in a phishing attack.