CVE-2025-7147
BaseFortify
Publication date: 2025-07-07
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| codeastro | patient_record_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-7147 is a critical Time-Based Blind SQL Injection vulnerability in the CodeAstro Patient Record Management System version 1.0. It affects the /login.php file, specifically the 'uname' parameter, which is improperly handled and allows attackers to inject malicious SQL commands. This flaw enables unauthenticated remote attackers to bypass authentication, extract sensitive data, and potentially compromise the entire database by exploiting weaknesses in input validation and query handling. [1, 2]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the system by bypassing login authentication, exposure and theft of sensitive patient data, and potential full compromise of the database. Since the system is a medical device software managing patient records, exploitation could lead to breaches of confidentiality, integrity, and availability of critical healthcare information. [1, 2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability poses significant risks to patient data security, which can lead to non-compliance with regulations such as GDPR and HIPAA that mandate protection of personal and health information. Exploitation could result in unauthorized disclosure or alteration of sensitive data, violating confidentiality and integrity requirements essential for these standards. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /login.php endpoint of the CodeAstro Patient Record Management System version 1.0 for SQL injection on the 'uname' parameter. One approach is to perform time-based blind SQL injection tests by injecting SQL payloads into the 'uname' parameter and observing response delays. Additionally, attackers may use Google dorking with queries like 'inurl:login.php' to identify potentially vulnerable targets. Specific commands could include using tools like curl or sqlmap to test the injection point, for example: curl -X POST -d "uname=' OR SLEEP(5)-- &password=anything" http://target/login.php to check for delayed responses indicating SQL injection. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
No known countermeasures or mitigations have been documented for this vulnerability. The recommended immediate step is to replace the affected software (CodeAstro Patient Record Management System version 1.0) with an alternative product. Additionally, as a temporary measure, restricting access to the /login.php endpoint and monitoring for suspicious activity may help reduce risk until a secure version or alternative is deployed. [2]