dbcve.org
InjectionWeakness · CWE-74

CVE-2026-10209

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
A vulnerability has been found in code-projects Online Hospital Management System 1.0. Affected is an unknown function of the file appointmentdetail.php of the component Appointment Handler. The manipulation of the argument editid leads to sql injection. The attack is possible to be carried out remotely. The exploit has been disclosed to the public and may be used.

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

SQL injection vulnerability in the appointmentdetail.php file of Online Hospital Management System 1.0 allows remote attackers to inject malicious SQL queries via the 'editid' parameter in the Appointment Handler component.

MitigationImplement prepared statements/parameterized queries for the editid parameter and conduct a broader code audit to identify and fix similar injection vulnerabilities throughout the application.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 Online Hospital Management System installation
    Search for the application files on the server. Common paths may include /var/www/html/, /htdocs/, or C:\inetpub\wwwroot\. Look for files like appointmentdetail.php, index.php, or login.php to confirm the application is present.
    Affected if The Online Hospital Management System 1.0 is installed and the appointmentdetail.php file exists in the web root.
  2. Determine the installed version
    Check for version indicators such as a version.php file, footer/copyright notices in PHP files, or a CHANGELOG/README file. Compare the found version number to 1.0.
    Affected if The installed version is 1.0 or if no version can be determined but the vulnerable file exists.
  3. Locate the vulnerable file
    Navigate to the web root and locate appointmentdetail.php. Open the file in a text editor or use 'grep' to search for the editid parameter usage.
    Affected if The file appointmentdetail.php exists and contains code handling the editid parameter.
  4. Inspect the SQL query handling for editid
    Examine the appointmentdetail.php file for SQL queries that incorporate the editid parameter directly without using prepared statements, parameter binding, or sanitization functions such as mysqli_real_escape_string or PDO::prepare.
    Affected if The code contains SQL queries where $_GET['editid'] or $_POST['editid'] is inserted directly into the query string without parameterization or escaping.
  5. Verify the component is accessible remotely
    Check if the Appointment Handler component or appointmentdetail.php is accessible via the web server. Attempt to access the URL directly, such as http://target/appointmentdetail.php?editid=1, to confirm it responds.
    Affected if The vulnerable endpoint is exposed and responds to HTTP requests containing the editid parameter.

If the Online Hospital Management System 1.0 is installed with appointmentdetail.php accessible and the editid parameter is used in unsanitized SQL queries, the environment is affected by this CVE.

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 prepared statements/parameterized queries for the editid parameter and conduct a broader code audit to identify and fix similar injection vulnerabilities throughout the application.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10209 — 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-10209 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