CVE-2025-7754
BaseFortify
Publication date: 2025-07-17
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 |
|---|---|---|
| fabianros | 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
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'itr_no' parameter in the /xray_form.php page for SQL injection. One approach is to send crafted HTTP requests with SQL injection payloads to the URL containing 'xray_form.php?itr_no=...'. For example, using curl or a web vulnerability scanner to inject SQL syntax such as a single quote (') or SQL tautologies. Additionally, Google dorking with the query 'inurl:xray_form.php' can help identify potentially vulnerable targets. Specific commands might include: curl -v "http://target/xray_form.php?itr_no=' OR '1'='1" or using sqlmap to automate detection: sqlmap -u "http://target/xray_form.php?itr_no=1" --batch. [2]
Can you explain this vulnerability to me?
CVE-2025-7754 is a critical SQL injection vulnerability in the code-projects Patient Record Management System version 1.0, specifically in the file /xray_form.php. The vulnerability occurs because the 'itr_no' parameter is used directly in an SQL query without proper input validation or sanitization. This allows an attacker to manipulate the 'itr_no' parameter to inject arbitrary SQL code remotely, potentially accessing or altering sensitive data in the database. [1, 2]
How can this vulnerability impact me? :
This vulnerability can allow remote attackers to execute arbitrary SQL commands on the affected system without authentication. Exploiting it can compromise the confidentiality, integrity, and availability of the system's data, potentially exposing sensitive patient information or disrupting system operations. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected software with an alternative product, as no official vendor patch or fix has been reported. Additionally, restricting access to the vulnerable endpoint, implementing web application firewall (WAF) rules to block malicious SQL injection attempts targeting the 'itr_no' parameter, and monitoring logs for suspicious activity are recommended. Input validation and sanitization should be applied if possible, but since the software is unpatched, replacement is the advised course of action. [2]