# CVE-2025-43925: Hardcoded credentials in n/a

> Attackers can decrypt the database using a hardcoded key to access cleartext data in Unicom Focal Point.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Jun 2025
- **Updated:** 3 Jun 2025
- **Also known as:** GHSA-3jrw-q59w-mpr2

## What is CVE-2025-43925?

CVE-2025-43925 is a medium-severity vulnerability in n/a, published on 3 Jun 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

An issue was discovered in Unicom Focal Point 7.6.1. The database is encrypted with a hardcoded key, making it easier to recover the cleartext data.

Weakness: CWE-326 (Inadequate Encryption Strength)

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

It affects 1 product.


Products: Unicomsi Focal Point.

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

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

## Is CVE-2025-43925 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-43923](https://insights.sbomify.com/CVE-2025-43923/): SQL injection in n/a (medium 6.5)
- [CVE-2025-43924](https://insights.sbomify.com/CVE-2025-43924/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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