dbcve.org
InjectionWeakness · CWE-74

CVE-2026-13542

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-29
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 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
A security vulnerability has been detected in itsourcecode Hospital Management System 1.0. Affected is an unknown function of the file /doctorprofile.php. The manipulation of the argument doctorname leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed publicly 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 itsourcecode Hospital Management System 1.0 allows remote attackers to inject malicious SQL queries via the doctorname parameter in /doctorprofile.php. The lack of input sanitization or parameterized queries in the doctor profile retrieval logic enables attackers to manipulate database queries.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries in doctorprofile.php, implement strict input validation on the doctorname parameter, and conduct a broader code audit for similar SQL injection flaws across 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 if itsourcecode Hospital Management System is installed
    Search for files or directories named 'hospital' or check web server document roots for itsourcecode Hospital Management System application files, particularly looking for doctorprofile.php
    Affected if The application itsourcecode Hospital Management System 1.0 is present on the server
  2. Locate the vulnerable doctorprofile.php file
    Navigate to the web root and search for the file path /doctorprofile.php or run: find / -name 'doctorprofile.php' 2>/dev/null
    Affected if The file doctorprofile.php exists in the web application directory
  3. Inspect the doctorname parameter handling in doctorprofile.php
    Open doctorprofile.php and examine how the 'doctorname' GET or POST parameter is retrieved and used in SQL queries - look for code like $_GET['doctorname'] or $_POST['doctorname'] being directly concatenated into SQL strings
    Affected if The doctorname parameter is retrieved and used directly in SQL queries without visible sanitization functions like mysqli_real_escape_string, htmlspecialchars, or input validation
  4. Verify whether parameterized queries are used
    Search the doctorprofile.php file for prepared statements, parameterized queries, or placeholder patterns such as '?', '$stmt', 'prepare', or 'bind_param' - their absence indicates vulnerability
    Affected if SQL queries in doctorprofile.php are constructed using string concatenation with the doctorname parameter rather than prepared statements or parameterized queries
  5. Check if the doctor profile feature is accessible
    Confirm the /doctorprofile.php endpoint is accessible on the web server by attempting to access it or reviewing web server access logs
    Affected if The doctorprofile.php endpoint is exposed and the application uses a MySQL or similar database backend

A user is affected if they are running itsourcecode Hospital Management System 1.0 with an accessible doctorprofile.php file that uses direct SQL query concatenation with the doctorname parameter instead of parameterized queries.

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

Replace dynamic SQL queries with prepared statements/parameterized queries in doctorprofile.php, implement strict input validation on the doctorname parameter, and conduct a broader code audit for similar SQL injection flaws across the application.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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