# CVE-2026-25861: QloApps 1.7.0 Weak Password Hashing via MD5 in Tools.php

> Attackers can compromise user credentials via offline brute-force attacks on weak MD5 password hashes in QloApps.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jun 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-xcxp-3whg-h83c

## What is CVE-2026-25861?

CVE-2026-25861 is a high-severity vulnerability in QloApps, published on 2 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

QloApps through 1.7.0, fixed in commit 64e9722, contains a weak cryptographic algorithm vulnerability that allows attackers to compromise user credentials by exploiting the use of MD5 for password hashing in the Tools::encrypt() function within classes/Tools.php, which concatenates a static cookie key with the supplied password. Attackers can perform offline brute-force attacks against the MD5 hashes, with the risk compounded by auto-generated 8-character passwords assigned during guest-to-customer account conversion in classes/Customer.php, making credential recovery trivial.

Weakness: CWE-916 (Use of Password Hash With Insufficient Computational Effort)

## Which versions are affected by CVE-2026-25861?


## How do I fix CVE-2026-25861?

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

## Is CVE-2026-25861 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25861 and fix it if it is affected.

What it is: CVE-2026-25861 is a high-severity vulnerability in QloApps, published on 2 Jun 2026. 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-2026-25861 in the wild and no public exploit code.

Affected product: QloApps. 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-2026-25861/ (Markdown: https://insights.sbomify.com/CVE-2026-25861/index.md)
```

## Sources

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

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