# CVE-2025-31966: Boolean-Based SQL Injection in Multiple Unica Components

> Attackers can bypass client-side validation to perform boolean-based SQL injection, potentially reading sensitive data from HCL Sametime.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Mar 2026
- **Updated:** 17 Mar 2026
- **Also known as:** GHSA-f5f8-5jp8-vj3c

## What is CVE-2025-31966?

CVE-2025-31966 is a low-severity SQL injection vulnerability in HCL Sametime, published on 17 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

HCL Sametime is vulnerable to broken server-side validation. While the application performs client-side input checks, these are not enforced by the web server. An attacker can bypass these restrictions by sending manipulated HTTP requests directly to the server.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Hcltech Sametime.

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

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

## Is CVE-2025-31966 being exploited?

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

## Other vulnerabilities in HCL Sametime

- [CVE-2021-27771](https://insights.sbomify.com/CVE-2021-27771/): HCL Sametime is susceptible a file transfer service vulnerability (high 8.2)
- [CVE-2021-27772](https://insights.sbomify.com/CVE-2021-27772/): HCL Sametime is vulnerable to an information disclosure (high 7.1)
- [CVE-2021-27770](https://insights.sbomify.com/CVE-2021-27770/): HCL Sametime is vulnerable to arbitrary HTTP requests (medium 6.8)
- [CVE-2022-42446](https://insights.sbomify.com/CVE-2022-42446/): HCL Sametime 12.0 and 12.0FP1 anonymous users have directory lookup access (medium 6.5)
- [CVE-2023-50349](https://insights.sbomify.com/CVE-2023-50349/): HCL Sametime is impacted by a Cross Site Request Forgery (CSRF) vulnerability (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-31966 is a low-severity SQL injection vulnerability in HCL Sametime, published on 17 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-31966 in the wild and no public exploit code.

Affected product: HCL Sametime. 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-31966/ (Markdown: https://insights.sbomify.com/CVE-2025-31966/index.md)
```

## Sources

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

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