dbcve.org
Hospital Management SystemApplication · Ponaravindb

CVE-2025-6339

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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 was found in ponaravindb Hospital Management System 1.0. It has been rated as critical. Affected by this issue is some unknown functionality of the file /func3.php. The manipulation of the argument username1 leads to sql injection. The attack may be launched 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 · high confidence

SQL injection vulnerability in ponaravindb Hospital Management System 1.0 in the /func3.php file via the username1 parameter allows remote attackers to inject arbitrary SQL commands. The CVSS 9.8 critical rating indicates potential for complete system compromise including data exfiltration or takeover.

MitigationReplace dynamic SQL queries with parameterized statements/prepared statements in func3.php for the username1 parameter. Apply input validation and output encoding as defense-in-depth. Given this is a hospital system handling sensitive patient data, prioritize rapid remediation and conduct a broader security assessment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Hospital Management SystemApplication
Affected:= 1.0

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 checks

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

  1. Confirm Ponaravindb Hospital Management System installation
    Locate the web application files in the web server document root. Look for files matching 'func3.php' or directories containing 'hospital' or 'ponaravindb' in the name.
    Affected if The application files are present on the system and version 1.0 is installed.
  2. Verify vulnerable file func3.php exists
    Search for the file func3.php in the web application directory structure. On typical LAMP/WAMP setups, this may be found under /var/www/html or C:\inetpub\wwwroot or similar web root paths.
    Affected if The file func3.php exists in the application directory.
  3. Check application version
    Inspect any version files, README files, or meta information within the application directory to confirm the installed version is exactly 1.0.
    Affected if The installed version is 1.0 (the only affected version per vendor disclosure).
  4. Verify the application is accessible over network
    Check if the web server hosting the application is reachable via HTTP/HTTPS on ports 80 or 443 (or configured alternate ports). Use curl, wget, or a browser to test connectivity to the application's login or main page.
    Affected if The application is network-accessible (even on localhost) and the vulnerable func3.php endpoint is reachable.
  5. Inspect func3.php for vulnerable code pattern
    If you have access to the source code, open func3.php and search for SQL query construction involving the 'username1' parameter without parameterized statements or prepared statements.
    Affected if The code contains direct string concatenation of the username1 parameter into SQL queries without using prepared statements or input sanitization.

The environment is affected if Ponaravindb Hospital Management System version 1.0 is installed with func3.php present and the vulnerable SQL injection code is in use, regardless of whether the application is exposed to the network.

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 parameterized statements/prepared statements in func3.php for the username1 parameter. Apply input validation and output encoding as defense-in-depth. Given this is a hospital system handling sensitive patient data, prioritize rapid remediation and conduct a broader security assessment.

Fix this in Hospital Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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