CVE-2025-6134
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-6134 is a critical SQL injection vulnerability in Projectworlds Life Insurance Management System version 1.0. It exists in the /insertClient.php file, specifically involving the client_id parameter. An attacker can manipulate this parameter to inject malicious SQL code, potentially compromising the database. The vulnerability allows remote exploitation without authentication and may affect other parameters as well. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by compromising the confidentiality, integrity, and availability of the affected system. An attacker exploiting this SQL injection flaw can access, modify, or delete sensitive data in the database remotely. This can lead to unauthorized data disclosure, data corruption, or disruption of service. [2]
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 endpoint /insertClient.php and testing the client_id parameter for SQL injection. One method is to use Google dorking with the query "inurl:insertClient.php" to identify potentially vulnerable targets. Additionally, manual or automated SQL injection testing tools can be used to test the client_id parameter for injection flaws. Specific commands are not provided in the resources. [2]
What immediate steps should I take to mitigate this vulnerability?
No known countermeasures or mitigations have been documented for this vulnerability. It is suggested to replace the affected component (Projectworlds Life Insurance Management System 1.0) with an alternative product to mitigate the risk. [2]