# CVE-2026-114119: Best Practice Software Bp Premier before 1.14.1.1128 Hardcoded SQL Server Administrative Credential


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-hmqc-m6cv-3c9r

## What is CVE-2026-114119?

CVE-2026-114119 is a critical vulnerability in Best Practice Software Bp Premier, published on 21 Oct 2026. 

### Official description

Best Practice Software Bp Premier before 1.14.1.1128 uses a hardcoded Microsoft SQL Server administrative password that is shared across all installations and cannot be changed without breaking the application. Attackers with network access to the database instance can authenticate as sysadmin, bypass application authentication, and execute operating system commands as SYSTEM.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2026-114119 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114119 is a critical vulnerability in Best Practice Software Bp Premier, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114119 in the wild and no public exploit code.

Affected product: Best Practice Software Bp Premier. 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-114119/ (Markdown: https://insights.sbomify.com/CVE-2026-114119/index.md)
```

## Sources

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

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