# CVE-2025-0642: Hard-coded Credentials in PosCube's Assist

> Hard-coded credentials in PosCube Assist allow attackers to bypass authentication and gain unauthorized access to the application.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N`)
- **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:** 2 Oct 2025
- **Updated:** 6 Jun 2026
- **Also known as:** AZL-110363, GHSA-w2m3-h5qg-m4mx

## What is CVE-2025-0642?

CVE-2025-0642 is a medium-severity vulnerability in PosCube Hardware Software and Consulting Ltd. Co. Assist, published on 2 Oct 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

Use of Hard-coded Credentials, Authorization Bypass Through User-Controlled Key vulnerability in PosCube Hardware Software and Consulting Ltd. Co. Assist allows Excavation, Authentication Bypass.

This issue affects Assist: through 10.02.2025.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2025-0642 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0642 is a medium-severity vulnerability in PosCube Hardware Software and Consulting Ltd. Co. Assist, published on 2 Oct 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-0642 in the wild and no public exploit code.

Affected product: PosCube Hardware Software and Consulting Ltd. Co. Assist. 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-0642/ (Markdown: https://insights.sbomify.com/CVE-2025-0642/index.md)
```

## Sources

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

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