dbcve.org
Life Insurance Management SystemApplication · Projectworlds

CVE-2025-6133

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 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.

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 · high confidence

SQL injection vulnerability in Projectworlds Life Insurance Management System 1.0 allows remote attackers to inject malicious SQL queries via the agent_id parameter in /insertagent.php. The lack of input sanitization or parameterized queries in the affected PHP file enables attackers to manipulate database queries, potentially leading to unauthorized data access, modification, or complete system compromise.

MitigationReplace dynamic SQL queries with parameterized queries (prepared statements) using PDO or mysqli, implement strict input validation on the agent_id parameter, and conduct a comprehensive code audit of the entire application to identify and remediate similar SQL injection vulnerabilities.

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. Identify the installed application version
    Locate the application files and check for version identifiers such as a version file, footer/version text in the UI, or check the source code headers. Compare against version 1.0.
    Affected if The installed version is Projectworlds Life Insurance Management System version 1.0.
  2. Verify the vulnerable file exists
    Check if the file /insertagent.php exists in the web root or application directory of the Life Insurance Management System installation.
    Affected if The file /insertagent.php is present in the application.
  3. Inspect the agent_id parameter handling
    Open /insertagent.php and search for the agent_id parameter usage in SQL queries. Look for direct insertion of the parameter into query strings without using prepared statements, parameter binding, or input sanitization functions.
    Affected if The agent_id parameter is used directly in SQL queries without parameterized queries (prepared statements), without mysqli/PDO binding, and without input sanitization.
  4. Confirm dynamic SQL query usage
    Examine the SQL query construction in /insertagent.php. Check if variables are concatenated or interpolated directly into SQL strings rather than using placeholders with bound parameters.
    Affected if The code constructs SQL queries by concatenating or interpolating the agent_id value directly into the query string.

The environment is affected if running Projectworlds Life Insurance Management System 1.0 with the file /insertagent.php present and the agent_id parameter being used in dynamically constructed SQL queries without parameterized queries or input sanitization.

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

Replace dynamic SQL queries with parameterized queries (prepared statements) using PDO or mysqli, implement strict input validation on the agent_id parameter, and conduct a comprehensive code audit of the entire application to identify and remediate similar SQL injection vulnerabilities.

Fix this in Life Insurance Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6133 — 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-6133 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