dbcve.org
Patient Record Management SystemApplication · Codeastro

CVE-2025-7147

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-07
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 has been found in CodeAstro Patient Record Management System 1.0 and classified as critical. Affected by this vulnerability is an unknown functionality of the file /login.php. The manipulation of the argument uname leads to sql injection. The attack can 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 CodeAstro Patient Record Management System 1.0's /login.php file. The 'uname' parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL code. This could enable authentication bypass, unauthorized access to patient records, or complete database compromise.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in login.php. Apply input validation on the uname parameter and ensure database user accounts follow least privilege principles.

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
Patient Record 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. Verify the CodeAstro Patient Record Management System version
    Locate and inspect any version file, header, or about page within the application. Check for a 'version' or 'release' file in the web root directory, or review the source code comments for version information.
    Affected if The installed version is exactly 1.0 (the only affected version listed)
  2. Locate the login.php file
    Navigate to the web root directory of the application and identify the /login.php file. This is typically found in the main web accessible directory.
    Affected if The login.php file exists and is accessible via the web server
  3. Inspect the 'uname' parameter handling in login.php
    Open login.php in a text editor or use 'grep' to search for the 'uname' parameter. Examine how the parameter is used in SQL queries - look for direct string concatenation or interpolation of $_POST['uname'] or $_REQUEST['uname'] into SQL statements without using prepared statements or parameter binding.
    Affected if The code shows direct insertion of the 'uname' parameter into SQL queries without sanitization, prepared statements, or parameterized queries
  4. Check database query implementation
    Search the login.php file for SQL query functions (such as mysqli_query, mysql_query, PDO::query, or similar). Examine whether the queries use '?' placeholders or named parameters with bound values, or if variables are concatenated directly into the query string.
    Affected if SQL queries concatenate user input directly rather than using parameterized query methods
  5. Test the parameter with diagnostic input
    Submit a benign test string such as "test'" in the 'uname' field on the login page and observe if SQL error messages are returned, or use a web proxy to capture the request and manually inject SQL syntax to check for SQL injection behavior.
    Affected if The application returns SQL syntax errors or exhibits unexpected behavior indicating the input is not being sanitized

A user is affected if they are running CodeAstro Patient Record Management System version 1.0 and the login.php file contains direct SQL query construction using the uname parameter without prepared statements.

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 queries/prepared statements in login.php. Apply input validation on the uname parameter and ensure database user accounts follow least privilege principles.

Fix this in Patient Record Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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