CVE-2025-7904
BaseFortify
Publication date: 2025-07-20
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 |
|---|---|---|
| angeljudesuarez | insurance_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-7904 is a critical SQL injection vulnerability in the itsourcecode Insurance Management System version 1.0, specifically in the /insertNominee.php file. The vulnerability occurs because the 'nominee_id' parameter is not properly validated or sanitized, allowing an attacker who has logged in with valid credentials to inject malicious SQL code. This can lead to unauthorized manipulation of the database, such as accessing, modifying, or deleting sensitive data. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can allow an attacker to manipulate SQL queries remotely after authentication, leading to unauthorized database access, data leakage, data tampering, full system control, and potential service disruption. It compromises the confidentiality, integrity, and availability of the system, posing a significant threat to system security and business continuity. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'nominee_id' parameter in the /insertNominee.php file for SQL injection flaws. Since exploitation requires authentication, you need valid credentials (e.g., username: ahmed, password: 12345) to perform testing. Tools like sqlmap can be used to automate detection by sending crafted POST requests with the 'nominee_id' parameter and a valid session cookie (PHPSESSID). Example sqlmap command: sqlmap -u "http://target/insertNominee.php" --data="nominee_id=1" --cookie="PHPSESSID=your_session_id" --risk=3 --level=5 --technique=BEUST --dbms=MySQL. Additionally, Google dorking with the query inurl:insertNominee.php can help identify potentially vulnerable targets on the network. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Enforce strict input validation and filtering on the 'nominee_id' parameter to ensure it matches expected numeric patterns. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. 4) Conduct regular security audits to detect and remediate vulnerabilities promptly. If possible, replace the affected component with an alternative product. These steps help prevent exploitation and reduce risk. [1, 3, 2]