CVE-2026-14807
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedERP 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe PROG MIS ERP application contains hardcoded credentials that allow unauthenticated remote attackers to bypass authentication entirely. Attackers can log in using these embedded credentials to access the application source code and retrieve database authentication details, leading to complete system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify PROG MIS ERP installationSearch the system for files or directories containing 'PROG MIS' or 'ERP' in the name. Check web server document roots, application directories, and any installed software locations.Affected if PROG MIS ERP application is found installed on the system
-
Locate application source codeFind the main application files - look for common source code extensions (.php, .asp, .js, .java, .py) and configuration files in the application directory.Affected if Source code files are present in the application directory
-
Search for hardcoded credentials in source codeUse grep or similar tools to search source files for patterns indicating hardcoded passwords: look for strings containing 'password', 'pwd', 'pass', 'credential', 'secret', 'key' assigned to literal values. Also search for base64-encoded strings that may contain credentials.Affected if Hardcoded password strings, API keys, or credential literals are found in source code files
-
Examine configuration files for embedded credentialsReview configuration files (config files, .env, settings files, XML/JSON configs) for database connection strings containing plaintext usernames and passwords, or for hardcoded administrative credentials.Affected if Configuration files contain plaintext database credentials or hardcoded admin account credentials
-
Check for authentication bypass mechanismsReview authentication-related code (login modules, session handlers, middleware) to identify if hardcoded credentials are being used as valid credentials for authentication bypass.Affected if Code contains hardcoded credentials that are accepted as valid login credentials
A user is affected if the PROG MIS ERP application is installed and its source code or configuration files contain hardcoded credentials that can be used to bypass authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately remove hardcoded credentials from the codebase and replace with secure credential management (e.g., environment variables, secrets vault). Rotate all exposed database credentials and implement proper authentication mechanisms. Conduct a full audit for additional hardcoded secrets.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14807 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-14807 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data