HCL iAutomate 6.5.1/6.5.2 get request method with sensitive query strings
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in HCL iAutomate 6.5.1/6.5.2. This vulnerability affects unknown code. Executing a manipulation can lead to use of get request method with sensitive query strings. This vulnerability is tracked as CVE-2025-31954. The attack can be launched remotely. No exploit exists.
Details
A vulnerability has been found in HCL iAutomate 6.5.1/6.5.2 and classified as problematic. This vulnerability affects some unknown functionality. The manipulation with an unknown input leads to a use of get request method with sensitive query strings vulnerability. The CWE definition for the vulnerability is CWE-598. The web application uses the HTTP GET method to process a request and includes sensitive information in the query string of that request. As an impact it is known to affect confidentiality. CVE summarizes:
HCL iAutomate v6.5.1 and v6.5.2 is susceptible to a sensitive information disclosure. An HTTP GET method is used to process a request and includes sensitive information in the query string of that request. An attacker could potentially access information or resources they were not intended to see.
The advisory is shared for download at support.hcl-software.com. This vulnerability was named CVE-2025-31954 since 04/01/2025. The exploitation appears to be easy. The attack can be initiated remotely. There are neither technical details nor an exploit publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.6
VulDB Base Score: 4.3
VulDB Temp Score: 4.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 4.3
NVD Vector: 🔒
CNA Base Score: 5.4
CNA Vector (HCL): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Use of get request method with sensitive query stringsCWE: CWE-598
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
04/01/2025 CVE reserved11/05/2025 Advisory disclosed
11/05/2025 VulDB entry created
11/08/2025 VulDB entry last update
Sources
Advisory: KB0125011Status: Not defined
CVE: CVE-2025-31954 (🔒)
GCVE (CVE): GCVE-0-2025-31954
GCVE (VulDB): GCVE-100-331312
Entry
Created: 11/05/2025 20:37Updated: 11/08/2025 15:34
Changes: 11/05/2025 20:37 (62), 11/08/2025 15:34 (11)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.