CVE-2025-6136VulnerabilityPublished 16 Jun 2025

CVE-2025-6136: Projectworlds Life Insurance Management System · SQL Injection

Affects Projectworlds Life Insurance Management SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubyzs17/Life_Insurance_Management_System`pkg:github/yzs17/Life_Insurance_Management_System`Other threats	Affected =1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate mitigation should include restricting external access to the /insertPayment.php endpoint through network segmentation, firewall rules, or VPN requirements to limit exposure. 2. Implement Web Application Firewall (WAF) rules specifically designed to detect and block SQL injection attempts targeting the 'recipt_no' parameter. 3. Conduct a thorough code review and apply input validation and parameterized queries or prepared statements to sanitize the 'recipt_no' input, eliminating injection vectors. 4. Monitor application logs for suspicious query patterns or repeated failed attempts to exploit this parameter. 5. Engage with Projectworlds vendor support to obtain or request an official patch or update addressing this vulnerability. 6. As a temporary workaround, consider disabling or restricting the functionality of the /insertPayment.php endpoint if feasible without disrupting critical operations. 7. Educate internal security teams and incident response units about this vulnerability to ensure rapid detection and response to potential exploitation attempts. 8. Perform penetration testing and vulnerability scanning focused on SQL injection to identify any other similar weaknesses in the system. These steps go beyond generic advice by focusing on specific endpoint controls, vendor engagement, and proactive detection tailored to this vulnerability.

Description

A vulnerability was found in Projectworlds Life Insurance Management System 1.0. It has been rated as critical. This issue affects some unknown processing of the file /insertPayment.php. The manipulation of the argument recipt_no leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using the Projectworlds Life Insurance Management System 1.0, this vulnerability poses a substantial risk to sensitive customer data, including personal and financial information. Successful exploitation could lead to unauthorized disclosure of confidential insurance records, manipulation of payment data, and disruption of insurance processing workflows. This could result in regulatory non-compliance with GDPR due to data breaches, financial losses, reputational damage, and potential legal liabilities. The medium CVSS score underestimates the potential impact in regulated environments where data integrity and confidentiality are paramount. Additionally, the ability to exploit remotely without user interaction increases the threat surface, especially for organizations with externally accessible management portals. The lack of known exploits in the wild currently limits immediate risk, but public disclosure may lead to rapid development of attack tools. Organizations relying on this system should consider the operational impact of potential downtime or data corruption, which could affect customer trust and business continuity.

Summary

CVE-2025-6136 is a SQL Injection vulnerability identified in version 1.0 of the Projectworlds Life Insurance Management System, specifically affecting the /insertPayment.php endpoint. The vulnerability arises from improper sanitization or validation of the 'recipt_no' parameter, which allows an attacker to inject malicious SQL code. This injection can be exploited remotely without requiring user interaction or authentication, as indicated by the CVSS vector (AV:N/AC:L/AT:N/UI:N/PR:L). The vulnerability impacts the confidentiality, integrity, and availability of the underlying database, potentially allowing unauthorized data access, modification, or deletion. The CVSS 4.0 base score is 5.3 (medium severity), reflecting that while the attack vector is network-based and requires low attack complexity, it does require some level of privileges (PR:L), possibly meaning a low-privileged authenticated user or a system with limited access. No public exploits are currently known in the wild, but the exploit details have been disclosed publicly, increasing the risk of exploitation. The lack of patches or mitigation links suggests that vendors have not yet released an official fix. Given the nature of the vulnerability and the criticality of the data handled by insurance management systems, this flaw represents a significant risk to data security and operational continuity.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Jun 2025, 20:04 UTC

Technical details

References

Community reviews

Related threats