# CVE-2025-31965: HCL BigFix Remote Control is affected by an authorization bypass vulnerability

> Non-admin users can view unauthorized information on certain web pages in HCL BigFix Remote Control Server WebUI due to improper access restrictions.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Jul 2025
- **Updated:** 29 Jul 2025
- **Also known as:** GHSA-hw93-rxq2-mqww

## What is CVE-2025-31965?

CVE-2025-31965 is a high-severity missing authorization vulnerability in HCL Software BigFix Remote Control, published on 29 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Improper access restrictions in HCL BigFix Remote Control Server WebUI (versions 10.1.0.0248 and lower) allow non-admin users to view unauthorized information on certain web pages.

Weakness: CWE-305 (Authentication Bypass by Primary Weakness)

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


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

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

## Is CVE-2025-31965 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-31965 is a high-severity missing authorization vulnerability in HCL Software BigFix Remote Control, published on 29 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-31965 in the wild and no public exploit code.

Affected product: HCL Software BigFix Remote Control. 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-31965/ (Markdown: https://insights.sbomify.com/CVE-2025-31965/index.md)
```

## Sources

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

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