# CVE-2025-52026: Information disclosure in n/a

> Unauthenticated access to a backend endpoint exposes MD5-hashed cashier credentials, allowing attackers to reverse hashes and gain unauthorized access.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jan 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-wfx8-p4c3-pcqp

## What is CVE-2025-52026?

CVE-2025-52026 is a high-severity vulnerability in n/a, published on 23 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An information disclosure vulnerability exists in the /srvs/membersrv/getCashiers endpoint of the Aptsys gemscms backend platform thru 2025-05-28. This unauthenticated endpoint returns a list of cashier accounts, including names, email addresses, usernames, and passwords hashed using MD5. As MD5 is a broken cryptographic function, the hashes can be easily reversed using public tools, exposing user credentials in plaintext. This allows remote attackers to perform unauthorized logins and potentially gain access to sensitive POS operations or backend functions.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Aptsys Gemscms Backend.

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

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

## Is CVE-2025-52026 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-52024](https://insights.sbomify.com/CVE-2025-52024/): Missing authorization in n/a (critical 9.4)
- [CVE-2025-52025](https://insights.sbomify.com/CVE-2025-52025/): SQL injection in n/a (critical 9.4)
- [CVE-2025-52022](https://insights.sbomify.com/CVE-2025-52022/): Information disclosure in n/a (medium 5.3)
- [CVE-2025-52023](https://insights.sbomify.com/CVE-2025-52023/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52026 is a high-severity vulnerability in n/a, published on 23 Jan 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-2025-52026 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-2025-52026/ (Markdown: https://insights.sbomify.com/CVE-2025-52026/index.md)
```

## Sources

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

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