# CVE-2025-31979: A File Upload Validation Bypass vulnerability has been identified in the HCL BigFix Service Management (SM)

> Attackers can upload malicious files like web shells by bypassing validation, leading to potential code execution on HCL BigFix SM.

- **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:** 28 Aug 2025
- **Updated:** 28 Aug 2025
- **Also known as:** GHSA-hj7g-h883-x979

## What is CVE-2025-31979?

CVE-2025-31979 is a medium-severity vulnerability in HCL Software BigFix Service Management (SM), published on 28 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A File Upload Validation Bypass vulnerability has been identified in the HCL BigFix SM, where the application fails to properly enforce file type restrictions during the upload process. An attacker may exploit this flaw to upload malicious or unauthorized files, such as scripts, executables, or web shells, by bypassing client-side or server-side validation mechanisms.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2025-31979 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-31979 is a medium-severity vulnerability in HCL Software BigFix Service Management (SM), published on 28 Aug 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-31979 in the wild and no public exploit code.

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

## Sources

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

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