CVE-2026-14808
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 · uneditedProg Management System developed by PROG MIS has a Exposure of Sensitive Information vulnerability, allowing unauthenticated remote attackers to view a specific page 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 · moderate confidenceThe Prog Management System (PROG MIS) contains an information disclosure vulnerability where a specific unauthenticated page exposes database credentials (username and password). Attackers can directly access this page remotely without any authentication to obtain plaintext database account credentials.
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.
-
Confirm PROG MIS installationLocate Prog Management System components on the server. Check for web application directories, installed services, or binaries named 'prog', 'progmis', or 'management system'. Query installed software inventories if available.Affected if PROG Management System is not installed on the target environment
-
Identify installed versionCheck application version files, About pages, or configuration headers within the PROG MIS installation directory. Compare against any available version documentation.Affected if Version cannot be determined or falls within an affected release range
-
Locate the exposed credentials pageSearch the web root for files or routes that may contain credential exposure functionality. Common paths include /config, /db, /setup, /backup, or similar directories. Look for pages with names suggesting database configuration like dbconfig, db_connect, or credentials.Affected if A page or endpoint exists that returns database connection strings or credential data
-
Test unauthenticated access to the credentials pageAttempt to access the identified page via HTTP/HTTPS request without providing any authentication credentials. Check if the response contains plaintext username and password fields for database access.Affected if The page returns database credentials (username/password) without requiring any login or session token
-
Verify authentication is required on sensitive pagesCompare access to known administrative or configuration endpoints. Confirm whether the credentials page redirects to a login form or returns a 401/403 error when accessed without authentication.Affected if Authentication is not enforced and sensitive configuration data is publicly accessible
If the Prog Management System is installed and a page displaying database credentials is accessible without any authentication, the environment is affected by CVE-2026-14808.
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 rotate the exposed database credentials and implement proper authentication/authorization controls on the vulnerable page. Restrict network access to the management system and audit for any unauthorized access.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14808 — 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-14808 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