# CVE-2025-31954: HCL iAutomate is susceptible to a sensitive information disclosure

> An attacker can access sensitive information by intercepting HTTP GET requests containing data in the query string.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Nov 2025
- **Updated:** 5 Nov 2025
- **Also known as:** GHSA-vghq-cm29-427c

## What is CVE-2025-31954?

CVE-2025-31954 is a medium-severity vulnerability in HCL Software iAutomate, published on 5 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-598 (Use of HTTP Request With Sensitive Query String)

## Which versions are affected by CVE-2025-31954?

It affects 1 product.


Products: Hcltech Dryice Iautomate.

## How do I fix CVE-2025-31954?

No fix has been published for CVE-2025-31954 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-31954 being exploited?

There is no known exploitation of CVE-2025-31954 in the wild and no public exploit code.

## Other vulnerabilities in HCL Software iAutomate

- [CVE-2025-31955](https://insights.sbomify.com/CVE-2025-31955/): HCL iAutomate is affected by a sensitive data exposure vulnerability (high 7.6)
- [CVE-2025-31952](https://insights.sbomify.com/CVE-2025-31952/): HCL iAutomate is affected by an insufficient session expiration (high 7.1)
- [CVE-2025-31953](https://insights.sbomify.com/CVE-2025-31953/): HCL iAutomate is affected by hardcoded credentials (high 7.1)
- [CVE-2023-23347](https://insights.sbomify.com/CVE-2023-23347/): Use of a broken cryptographic algorithm affects HCL DRYiCE iAutomate (medium 6.4)
- [CVE-2024-42207](https://insights.sbomify.com/CVE-2024-42207/): HCL iAutomate is affected by a session fixation vulnerability (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-31954 and fix it if it is affected.

What it is: CVE-2025-31954 is a medium-severity vulnerability in HCL Software iAutomate, published on 5 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-31954 in the wild and no public exploit code.

Affected product: HCL Software iAutomate. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-31954/ (Markdown: https://insights.sbomify.com/CVE-2025-31954/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-31954
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-31954
- OSV: https://osv.dev/vulnerability/CVE-2025-31954

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-31954/
Summaries are generated and may contain mistakes; the official description above is the record.