dbcve.org
Life Insurance Management SystemApplication · Projectworlds

CVE-2025-6134

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was found in Projectworlds Life Insurance Management System 1.0. It has been classified as critical. This affects an unknown part of the file /insertClient.php. The manipulation of the argument client_id leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. Other parameters might be affected as well.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SQL injection vulnerability in the client_id parameter of /insertClient.php in Projectworlds Life Insurance Management System 1.0 allows remote attackers to inject arbitrary SQL commands. The CVSS 9.8 critical score indicates trivial exploitability with potentially complete system compromise. Other parameters in the same file may also be vulnerable.

MitigationImplement prepared statements/parameterized queries for all database operations in insertClient.php and audit other parameters/files for similar SQL injection flaws.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Life Insurance Management SystemApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Projectworlds Life Insurance Management System is installed
    Locate the application by searching for files named 'insertClient.php' or directories containing 'Life Insurance Management' or 'Projectworlds' on the web server. Check web server document roots (e.g., /var/www/html, /htdocs, C:\inetpub\wwwroot) for the application.
    Affected if The application files are found on the server
  2. Verify the installed version is 1.0
    Check for a version file, README, or any file containing 'version' or '1.0' within the application directory. Look in files like version.php, about.php, or the root directory for version information.
    Affected if The version is confirmed as 1.0
  3. Locate insertClient.php
    Find insertClient.php in the web-accessible directory structure. Common paths may include /admin/, /php/, or the root of the application.
    Affected if insertClient.php exists in the application
  4. Examine client_id parameter handling in insertClient.php
    Open insertClient.php and inspect how the client_id parameter is processed. Look for direct inclusion of the parameter in SQL queries without prepared statements, parameter binding, or input sanitization.
    Affected if The client_id parameter is concatenated directly into SQL queries without escaping or parameterization
  5. Test client_id parameter for SQL injection
    If direct code inspection is not possible, attempt benign SQL injection tests on the client_id parameter in insertClient.php using a safe payload (e.g., ' OR '1'='1) while monitoring for SQL errors or unexpected behavior. Only test on non-production systems with authorization.
    Affected if SQL syntax errors appear or the query behaves unexpectedly, indicating unsanitized input acceptance
  6. Audit other parameters in insertClient.php
    Review all other parameters received by insertClient.php (e.g., via $_POST, $_GET, $_REQUEST) and check if they are used in SQL queries without proper escaping or prepared statements.
    Affected if Any other parameter is found to be concatenated into SQL queries without protection

The environment is affected if Projectworlds Life Insurance Management System version 1.0 is installed and insertClient.php contains direct SQL query construction using the client_id parameter or other unsanitized inputs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement prepared statements/parameterized queries for all database operations in insertClient.php and audit other parameters/files for similar SQL injection flaws.

Fix this in Life Insurance Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6134 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-6134 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data