CVE-2025-6135
BaseFortify
Publication date: 2025-06-16
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 |
|---|---|---|
| projectworlds | life_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-6135 is a critical SQL injection vulnerability in Projectworlds Life Insurance Management System version 1.0, specifically in the /insertNominee.php file. It arises from improper handling and sanitization of the client_id and nominee_id parameters, allowing an attacker to inject malicious SQL commands remotely without authentication. This flaw enables execution of arbitrary SQL commands, potentially compromising the system's confidentiality, integrity, and availability. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can allow remote attackers to execute arbitrary SQL commands on the affected system, leading to unauthorized access to sensitive data, data leakage, modification or deletion of data, and disruption of system availability. It compromises the confidentiality, integrity, and availability of the Life Insurance Management System, potentially causing significant operational and security impacts. [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 checking for the presence of the vulnerable file /insertNominee.php on your system or web server. Additionally, you can use Google dorking with the query 'inurl:insertNominee.php' to identify potentially vulnerable targets exposed on the internet. To detect exploitation attempts on your network, monitor HTTP requests for suspicious or malformed parameters 'client_id' and 'nominee_id' that may contain SQL injection payloads. Specific commands are not documented, but you can use web server logs or intrusion detection systems to filter requests containing these parameters with unusual characters or SQL syntax. [1]
What immediate steps should I take to mitigate this vulnerability?
No known countermeasures or mitigations have been documented for this vulnerability. The suggested immediate step is to replace the affected component (Projectworlds Life Insurance Management System version 1.0) with an alternative product that is not vulnerable. Additionally, restricting access to the vulnerable endpoint and monitoring for exploitation attempts may help reduce risk until a fix or patch is available. [1]