Skip to main content
VulnerabilityPublished

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

Affects Projectworlds Life Insurance Management SystemSource CVE Database V5

0

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 17:16 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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Projectworlds Life Insurance Management SystemAffected
  • =1.0
Fixed in–

AI-suggested

  1. Immediate mitigation should include implementing web application firewall (WAF) rules to detect and block SQL injection attempts targeting the 'agent_id' parameter in /insertagent.php.
  2. Conduct a thorough code review and input validation enhancement for all parameters, especially 'agent_id', applying parameterized queries or prepared statements to eliminate SQL injection risks.
  3. Restrict database user permissions to the minimum necessary, preventing unauthorized data modification or extraction even if injection occurs.
  4. Monitor application logs and network traffic for unusual query patterns or repeated access attempts to /insertagent.php.
  5. If possible, isolate the vulnerable application instance from critical internal networks to limit lateral movement.
  6. Engage with the vendor for official patches or updates and plan for timely application once available.
  7. Perform regular security assessments and penetration testing focusing on injection vulnerabilities.
  8. Educate development and operations teams about secure coding practices and the importance of input sanitization. These steps go beyond generic advice by focusing on immediate protective controls, least privilege enforcement, and proactive detection tailored to the specific vulnerable component.

Description

A vulnerability was found in Projectworlds Life Insurance Management System 1.0 and classified as critical. Affected by this issue is some unknown functionality of the file /insertagent.php. The manipulation of the argument agent_id leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…