dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-14809

HIGH · 7.5 CVSS v3.1 Published 2026-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 7 weeks old

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 · unedited
Prog Management System developed by PROG MIS has a SQL Injection vulnerability, allowing unauthenticated remote attackers to inject arbitrary SQL commands to read database contents.

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 confidence

The Prog Management System by PROG MIS contains an SQL Injection vulnerability in one or more input fields that are not properly sanitized before being used in database queries. An unauthenticated remote attacker can craft malicious SQL payloads to bypass authentication and extract sensitive data from the underlying database, potentially exposing user credentials, application data, and other confidential information.

MitigationImplement parameterized queries (prepared statements) or stored procedures for all database interactions, apply input validation and output encoding, and restrict database permissions to the minimum required for the application to function.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Prog Management System is installed
    Search for application files, check for 'Prog Management System' or 'PROG MIS' strings in web directories, or look for characteristic login pages, configuration files, or database connection files that reference this product
    Affected if The application files or instances of Prog Management System by PROG MIS are found in the environment
  2. Determine the installed version
    Check version files, about pages, or configuration files within the application directory for version strings; compare against any available version documentation from the vendor
    Affected if The installed version falls within a vulnerable range or cannot be determined (assume affected)
  3. Identify input fields that handle authentication or data queries
    Review application source code, web forms, or API endpoints for input fields that interact with database queries, particularly login forms, search fields, or parameters that accept user input and pass it to database operations
    Affected if Input fields exist that accept user-supplied data and are used in database queries without visible sanitization
  4. Check for proper SQL query handling
    Examine the application's database interaction code (source code or decompiled files) for use of prepared statements, parameterized queries, or stored procedures versus string concatenation in SQL queries
    Affected if SQL queries are constructed using string concatenation or unsanitized string interpolation rather than parameterized queries
  5. Test affected input fields for SQL injection
    Using a safe testing methodology, submit SQL injection test payloads (such as single quotes, UNION-based payloads, or time-based payloads) to identified input fields and observe for SQL errors, unexpected behavior, or time delays that indicate successful injection
    Affected if Submitting SQL injection payloads produces database errors, bypasses authentication, or reveals unexpected data
  6. Review database user permissions
    Inspect database user accounts used by the application to determine if they have excessive privileges beyond what the application requires (such as administrative privileges or access to other databases)
    Affected if The application database user has elevated privileges that could allow an attacker to escalate impact beyond the application database

The environment is affected if Prog Management System by PROG MIS is installed and input fields used in database queries do not use parameterized queries, allowing unauthenticated SQL injection attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries (prepared statements) or stored procedures for all database interactions, apply input validation and output encoding, and restrict database permissions to the minimum required for the application to function.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14809 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-14809 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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