# CVE-2021-25839: Weak cryptography in n/a

> Weak password requirements in MintHCM allow attackers to easily brute-force user accounts, potentially leading to unauthorized access.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Apr 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-gmp2-cx4g-4hx8

## What is CVE-2021-25839?

CVE-2021-25839 is a critical vulnerability in n/a, published on 26 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A weak password requirement vulnerability exists in the Create New User function of MintHCM RELEASE 3.0.8, which could lead an attacker to easier password brute-forcing.

Weakness: CWE-521 (Weak Password Requirements)

## Which versions are affected by CVE-2021-25839?

It affects 1 product.


Products: Minthcm Minthcm.

## How do I fix CVE-2021-25839?

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

## Is CVE-2021-25839 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-36656](https://insights.sbomify.com/CVE-2024-36656/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2021-25838](https://insights.sbomify.com/CVE-2021-25838/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-25839 and fix it if it is affected.

What it is: CVE-2021-25839 is a critical vulnerability in n/a, published on 26 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-25839 in the wild and no public exploit code.

Affected product: n/a. 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-2021-25839/ (Markdown: https://insights.sbomify.com/CVE-2021-25839/index.md)
```

## Sources

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

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