# CVE-2026-14807: PROG MIS｜ERP App - Use of Hard-coded Credentials

> Unauthenticated attackers can use hard-coded credentials to log in, view application code, and obtain database credentials in PROG MIS ERP App.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** GHSA-8xw6-3xrm-fqhg

## What is CVE-2026-14807?

CVE-2026-14807 is a critical vulnerability in PROG MIS ERP App, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ERP App developed by PROG MIS has a Use of Hard-coded Credentials vulnerability, allowing unauthenticated remote attackers to log in to view application code and obtain the database account and password.

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

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


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

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

## Is CVE-2026-14807 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14807 is a critical vulnerability in PROG MIS ERP App, published on 6 Jul 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-14807 in the wild and no public exploit code.

Affected product: PROG MIS ERP App. 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-14807/ (Markdown: https://insights.sbomify.com/CVE-2026-14807/index.md)
```

## Sources

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

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