VulnerabilityPublished 5 Nov 2025

CVE-2025-31954: HCL Software iAutomate · Use of GET Request Method With Sensitive Query Strings

Affects HCL Software iAutomateSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% 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:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Nov 2025
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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
HCL Software iAutomate	Affected =6.5.1 =6.5.2	Fixed in–

AI-suggested

European organizations should immediately audit their use of HCL iAutomate versions 6.5.1 and 6.5.2 to identify any workflows or API calls that transmit sensitive information via HTTP GET requests. Where possible, modify these workflows to use HTTP POST or other methods that place sensitive data in the request body rather than the URL. Implement strict access controls and monitoring on logs and network traffic to detect unauthorized access to URLs containing sensitive data. Employ network segmentation and encryption (e.g., TLS) to protect data in transit. Review and minimize the privileges of users and service accounts interacting with iAutomate to reduce the risk of exploitation by insiders or compromised accounts. Since no patches are currently available, consider temporary compensating controls such as disabling vulnerable endpoints or restricting access to trusted networks. Educate developers and administrators on secure coding practices to avoid embedding sensitive data in URLs. Finally, maintain vigilance for any updates or patches from HCL and apply them promptly once released.

Description

CVE-2025-31954 is a medium severity vulnerability affecting HCL Software's iAutomate versions 6.5.1 and 6.5.2. The issue arises from the use of HTTP GET requests that include sensitive information within the query string, potentially exposing confidential data. An attacker with at least limited privileges could intercept or access these URLs and gain unauthorized insight into sensitive information. Exploitation does not require user interaction but does require some level of privilege. The vulnerability impacts confidentiality and integrity but not availability. No known exploits are currently in the wild, and no patches have been released yet.

Impact

For European organizations, this vulnerability poses a risk of sensitive information leakage, which could include credentials, tokens, or confidential parameters embedded in URLs. Such exposure could lead to unauthorized access to internal resources or data breaches, undermining data protection compliance such as GDPR. The integrity impact suggests potential manipulation of automation workflows, which could disrupt business processes or lead to incorrect operations. Organizations in sectors with strict data privacy requirements (e.g., finance, healthcare, government) are particularly at risk. The lack of availability impact reduces the risk of service disruption but does not diminish the confidentiality concerns. Since exploitation requires some privilege, insider threats or compromised accounts could leverage this vulnerability. The absence of known exploits provides a window for remediation before active attacks emerge. However, the widespread use of HCL iAutomate in European enterprises for automation tasks means that the vulnerability could have broad implications if not addressed promptly.

CWE-598Use of HTTP Request With Sensitive Query String (opens in a new tab)
Variant weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The web application uses an HTTP method to process a request, but the request includes sensitive information in the query string.
Implementation
When sending sensitive information, only include it in the request body or request headers instead of the query string. This may require avoiding use of GET requests.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Web Service Security (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V3.1.1 (opens in a new tab)
V13.1.3 (opens in a new tab)
V8.3.4 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0125011 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Nov 2025, 18:56 UTC

WeaknessesCWE-598

Technical details

References

Community reviews

Related threats